Comment 2 for bug 206406

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexander Belchenko wrote:
| Alexander Belchenko пишет:
|> Public bug reported:
|>
|> bzr 1.3 @ win32: local push finished with error message: Could not
|> acquire lock
|> Operation almost done. Build phase is done, repository is OK,
|> working tree successfully created.
|
| This bug introduced by revno.3279 in bzr.dev:
|
| revno: 3279
| committer: Canonical.com Patch Queue Manager <email address hidden>
| branch nick: +trunk
| timestamp: Sat 2008-03-15 01:07:14 +0000
| message:
| (jam) Implement Cherrypick support for Merge3
|

I'm guessing it is just exposing a latent bug where we were not locking when we
should.

Specifically, the cherrypick requires grabbing ancestry (which would have been
required with a different merge algorithm anyway), so it needs a read-lock for a
period of time.

This would indicate that we should have either been taking out a write lock
earlier (and the read is now conflicting when we do take out a write-lock), or
something similar.

I'm not at much liberty to work on this right now, mostly because the internet
access here is quite limited. I get about 4.5KB/s for a couple of hours, which
is almost enough to get all of my email.

So my quick answer is to just check if you can get a lock taken out earlier. It
might also be that I'm taking a tree read lock, when really all I need is a
branch/repository level one.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH7X3pJdeBCYSNAAMRAk4+AJ9Y/Y9sYjZ7oSiSGDy/cVaPP3bqCwCdHVgA
x0wU5mGJ9pHfOZWREqnmx4g=
=aQ5Y
-----END PGP SIGNATURE-----