Trouble pushing to repository via svn+ssh:// and file://

Bug #251428 reported by Berto
2
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
Invalid
Medium
Berto
subversion
New
Undecided
Unassigned

Bug Description

I've tried to push changes from a bzrsvn repository back into svn without success. I've tried the two methods available in my environment; via file:/// and svn+ssh://. I am pretty sure it's not a permissions issue on the repository because I'm able to interact with it just fine over svn+ssh. I also tried upgrading svn to the trunk, which did not help in this case. I always end up with the error:

SubversionException: ("Can't write to connection: Bad address", 14)

Below is a full trace from ~/.bzr.log:

0.046 encoding stdout as sys.stdout encoding 'UTF-8'
0.046 bzr arguments: [u'push', u'svn+ssh://dev01.local/home/dev/repo.svn']
0.047 looking for plugins in /home/berto/.bazaar/plugins
0.107 looking for plugins in /opt/bzr/bzr.dev/bzrlib/plugins
0.107 Plugin name __init__ already loaded
0.107 Plugin name __init__ already loaded
0.135 bzr-svn: using Subversion 1.6.0 (-dev)
0.137 looking for plugins in /usr/lib/python2.5/site-packages/bzrlib/plugins
0.139 encoding stdout as sys.stdout encoding 'UTF-8'
0.153 opening SVN RA connection to 'svn+ssh://dev01.local/home/dev/repo.svn'
[17686] 2008-07-24 01:25:12.915 WARNING: using experimental bzr-svn mappings; ma
y break existing branches in the most horrible ways
1.866 pushing 'roberto.aguilar@local-20080724074403-khcy3ec5cr4q1trz' (['svn-v3
-none:d809f9fd-43ca-4870-99a1-df1fa70c1007::1103'])
3.867 Traceback (most recent call last):
  File "/opt/bzr/bzr.dev/bzrlib/commands.py", line 857, in run_bzr_catch_errors
    return run_bzr(argv)
  File "/opt/bzr/bzr.dev/bzrlib/commands.py", line 797, in run_bzr
    ret = run(*run_argv)
  File "/opt/bzr/bzr.dev/bzrlib/commands.py", line 499, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/opt/bzr/bzr.dev/bzrlib/builtins.py", line 788, in run
    use_existing_dir=use_existing_dir)
  File "/opt/bzr/bzr.dev/bzrlib/push.py", line 172, in _show_push_branch
    stop_revision=revision_id)
  File "/opt/bzr/bzr.dev/bzrlib/decorators.py", line 138, in read_locked
    result = unbound(self, *args, **kwargs)
  File "/opt/bzr/bzr.dev/bzrlib/branch.py", line 1756, in push
    _override_hook_source_branch=_override_hook_source_branch)
  File "/opt/bzr/bzr.dev/bzrlib/branch.py", line 1798, in _push_with_bound_branc
hes
    result = self._basic_push(target, overwrite, stop_revision)
  File "/opt/bzr/bzr.dev/bzrlib/branch.py", line 1821, in _basic_push
    graph=graph)
  File "/opt/bzr/bzr.dev/bzrlib/plugins/svn/branch.py", line 513, in update_revi
sions
    push(self, other, revid)
  File "/opt/bzr/bzr.dev/bzrlib/plugins/svn/commit.py", line 806, in push
    rev, push_metadata=push_metadata)
  File "/opt/bzr/bzr.dev/bzrlib/plugins/svn/commit.py", line 765, in push_revisi
on_tree
    revid = builder.commit(rev.message)
  File "/opt/bzr/bzr.dev/bzrlib/plugins/svn/commit.py", line 531, in commit
    branch_editors[-1].change_prop(prop, value)
SubversionException: ("Can't write to connection: Bad address", 14)

3.868 return code 4

Thanks!

Revision history for this message
Berto (bertosmailbox) wrote :

With the latest revs of software, I no longer get "Can't write to connection [...]", but I still cannot push.

bzr revno: 3589
bzrsvn revno: 1504
svn: r32321

Here is the new log:

0.200 encoding stdout as sys.stdout encoding 'UTF-8'
0.205 bzr arguments: [u'-Dhpss', u'push']
0.205 looking for plugins in /Users/berto/.bazaar/plugins
0.263 bzr-svn: using Subversion 1.6.0 (-dev)
0.347 looking for plugins in /Users/berto/local/opt/bzr/bzrlib/plugins
0.347 Plugin name __init__ already loaded
0.347 Plugin name __init__ already loaded
0.348 looking for plugins in /Library/Python/2.5/site-packages/bzrlib/plugins
0.351 encoding stdout as sys.stdout encoding 'UTF-8'
0.391 opening SVN RA connection to 'svn+ssh://<email address hidden>/home/dev/repo.svn'
[83006] 2008-07-29 09:56:50.757 WARNING: using experimental bzr-svn mappings; may break existing branches in the most horrible ways
1.508 pushing '<email>@gmail.com-20080729163941-h13owgav61418o4p' (['svn-v3-none:d809f9fd-43ca-4870-99a1-df1fa70c1007::1135'])
4.153 Traceback (most recent call last):
  File "/Users/berto/local/opt/bzr/bzrlib/commands.py", line 857, in run_bzr_catch_errors
    return run_bzr(argv)
  File "/Users/berto/local/opt/bzr/bzrlib/commands.py", line 797, in run_bzr
    ret = run(*run_argv)
  File "/Users/berto/local/opt/bzr/bzrlib/commands.py", line 499, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/Users/berto/local/opt/bzr/bzrlib/builtins.py", line 788, in run
    use_existing_dir=use_existing_dir)
  File "/Users/berto/local/opt/bzr/bzrlib/push.py", line 172, in _show_push_branch
    stop_revision=revision_id)
  File "/Users/berto/local/opt/bzr/bzrlib/decorators.py", line 138, in read_locked
    result = unbound(self, *args, **kwargs)
  File "/Users/berto/local/opt/bzr/bzrlib/branch.py", line 1779, in push
    _override_hook_source_branch=_override_hook_source_branch)
  File "/Users/berto/local/opt/bzr/bzrlib/branch.py", line 1821, in _push_with_bound_branches
    result = self._basic_push(target, overwrite, stop_revision)
  File "/Users/berto/local/opt/bzr/bzrlib/branch.py", line 1844, in _basic_push
    graph=graph)
  File "/Users/berto/.bazaar/plugins/svn/branch.py", line 513, in update_revisions
    push(self, other, revid)
  File "/Users/berto/.bazaar/plugins/svn/commit.py", line 806, in push
    rev, push_metadata=push_metadata)
  File "/Users/berto/.bazaar/plugins/svn/commit.py", line 765, in push_revision_tree
    revid = builder.commit(rev.message)
  File "/Users/berto/.bazaar/plugins/svn/commit.py", line 499, in commit
    done, None, False)
  File "/Users/berto/.bazaar/plugins/svn/errors.py", line 140, in convert
    raise convert_error(e)
SubversionException: (None, 210007)

4.156 return code 4

Thanks!

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

210007 is SVN_ERR_RA_SVN_NO_MECHANISMS

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

This basically means that svn was unable to negotiate the authentication credentials. There's not much that can be done about this in bzr-svn, except perhaps a clearer error message.

Revision history for this message
Berto (bertosmailbox) wrote :

I would agree with this hypothesis, but I am able to branch the SVN repository just fine. Once I have a repository on my end and make a commit to it I am then unable to push stuff back.

Seeing as I can clone the repository using bzrsvn I don't believe it would be an authentication issue.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

It's quite common for svn repositories to only require authentication on commit, not when branching.

Revision history for this message
Berto (bertosmailbox) wrote :

Tim Hatch pointed out this:

[22:48] <jelmer> matid: in other words, configuring with --without-sasl may fix it

from:

http://irclogs.ubuntu.com/2008/04/12/%23bzr.html

and from:

http://www.nabble.com/Crazy-svn%2Bssh-commit-regression-in-trunk-and-1.5-td15349239.html#a15418829

This appears to be svn + SASL issue. I recompiled the trunk version of svn with:

--without-sasl

And things are now working, great!

Attached is a patch to give a description of the error message.

Jelmer Vernooij (jelmer)
Changed in bzr-svn:
assignee: nobody → bertosmailbox
importance: Undecided → Medium
milestone: none → 0.4.11
status: New → Fix Committed
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Any chance you can use the constant rather than the hardcoded error number?

Also, please keep the regular error message intact but only hint the user may have hit this svn bug - it may also be possible that this error happens genuinely.

Changed in bzr-svn:
status: Fix Committed → In Progress
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Closing bzr-svn portion of this report - this is a bug in SASL or Subversion. At the very least, the error message from Subversion could be clearer.

Changed in bzr-svn:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.