svn-push has uncaught SubversionException 170001

Bug #267899 reported by Alexey Borzenkov
2
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
Fix Released
Undecided
Jelmer Vernooij

Bug Description

Steps to reproduce:

1. Create a new repository on your server (svnadmin create testme). Don't edit svnserver.conf and leave everything at its defaults.
2. Create a simple bzr branch with at least one revision in it.
3. Try bzr svn-push <your-server>/testme/trunk

You will see a traceback with SubversionException: (None, 170001), which is Authorization error.

Please see part of .bzr.log with a traceback attached.

Revision history for this message
Alexey Borzenkov (snaury) wrote :
Jelmer Vernooij (jelmer)
Changed in bzr-svn:
assignee: nobody → jelmer
milestone: none → 0.4.13
status: New → Fix Committed
Jelmer Vernooij (jelmer)
Changed in bzr-svn:
status: Fix Committed → Fix Released
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

This is a bug in Subversion, caused by there not being any worthy authentication mechanisms. Does committing to svn manually work?

Changed in bzr-svn:
status: Fix Released → New
Revision history for this message
Alexey Borzenkov (snaury) wrote :

Jelmer, no-no-no. This bug is only about traceback instead of an error message. svn-push should *not* (and can't) succeed in this scenario. svn gives "svn: Authorization failed" error message, which is correct behavior.

Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 267899] Re: svn-push has uncaught SubversionException 170001

Am Donnerstag, den 25.09.2008, 19:14 +0000 schrieb Alexey Borzenkov:
> Jelmer, no-no-no. This bug is only about traceback instead of an error
> message. svn-push should *not* (and can't) succeed in this scenario. svn
> gives "svn: Authorization failed" error message, which is correct
> behavior.
In that case, your bug report is incomplete. Please provide more
 information (such as a traceback) about how to reproduce this.
 Pushing to a svn:// URL doesn't raise such an exception but
 correctly prints a "Readonly connection" error. The generic exception
 converter also already handles 170001.

Cheers,

Jelmer
--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>

Revision history for this message
Alexey Borzenkov (snaury) wrote :

Jelmer, why is it incomplete? Isn't it already fixed?

It currently prints:
bzr: ERROR: Permission denied: "."

Which sounds pretty correct to me. :-/

Try for yourself:

bzr init myrepo2
cd myrepo2
echo "Some text here" >a.txt
bzr add && bzr commit -m "Initial commit"
bzr svn-push svn://kitsu.ru/empty-no-access/trunk

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

Sorry, something seems to've gone wrong here. I thought you were
reporting a new bug, but that doesn't appear to be the case.

  status fixreleased
--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>

Changed in bzr-svn:
status: New → Fix Released
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.