Hello, * Andres Salomon [Wed, May 31, 2006 at 09:19:49AM -0400]: > Hi, > > On Wed, 2006-05-31 at 10:16 +0200, Laurent Fousse wrote: > > found 368760 0.8.2-3 > > thanks > > > > Hello, > > > > The bug is still present in 0.8.2-3 : > > > > This is a different bug; and actually, I'm not sure it's a bug at all. > bzr push needs to be able to write to whereever is being pushed to, and > uses absolute paths. It looks like you're trying to create a repository > in / on nowwhat.lateralis.org. You probably need to be root to do that.
Before the upgrade I had a working repository with a similar path, and it was understood as relative to my homedir. So it's a change in behaviour (worth documenting in NEWS.Debian perhaps). And when performing the action described in my report, I see the directory being created by `bzr push', and these directories are relative to my homedir. See: $ bzr push --create-prefix sftp://topaz.conuropsis.org/THIS_IS_A_BUG bzr: ERROR: No such file: '/THIS_IS_A_BUG': No such file: unable to stat Exception exceptions.AttributeError: "'LockableFiles' object has no attribute '_lock_count'" in <bound method LockableFiles.__del__ of LockableFiles(<bzrlib.transport.sftp.SFTPTransport url=sftp://topaz.conuropsis.org/THIS_IS_A_BUG/>)> ignored I can understand that it fails because I should use an absolute path. But then, why does it create ~/THIS_IS_A_BUG on topaz ? In any case, the uncaught exception is a bug. Thanks for the pointer on absolute path, the repository is usable again. Laurent. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
