error while updating/upgrading exaile

[Robert Collins]

On Mon, 2007-09-24 at 08:13 +0200, Vincent Ladeuil wrote:


>     robert> It certainly used to be, the remote branch is not altered by commit.
> 
> Sure if he commits locally, but he did a bzr update.

Even so, doing update should never need to lock the master branch.

> May be bzr unbind is appropriate here, I can't deduce the setup
> used from the backtrace.
> 
> If update uses:
> 
> parent = remote1
> master = remote1
> branch = local1
> working tree = local2
> 
> Then bzr unbind should be ok.

I'm saying that update as is *should work*.

'parent' is not involved in 'update' at all.

> if it's:
> 
> parent = remote1
> master = remote2
> branch = local1
> working tree = local2
> 
> then 'bzr bind sftp://remote2 or bzr+ssh://remote2' should do.
> 
> My last modification was about reusing the master transport, I
> don't think I modified any other behavior by doing that.

Ok, then it must be something else.

-Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070924/c5188bb6/attachment.pgp