Comment 15 for bug 152746

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

Kees Cook wrote:
> I suddenly can't commit to https://code.launchpad.net/~ubuntu-security
> /ubuntu-cve-tracker/master anymore; I'm hitting this bug. While it
> hung, it did eventually fail:
>
> $ bzr ci -m 'add CVE for e2fsprogs'
> No handlers could be found for logger "bzr"
> bzr: ERROR: Could not acquire lock "(remote lock)"
>
> Is there a work-around for this?
>

When you run into it, do ^C

Then
bzr break-lock bzr+ssh://bazaar.launchpad.net/~ubuntu-security/...
bzr break-lock bzr+ssh://bazaar.launchpad.net/~ubuntu-security/...

You have to run 2 break-locks, because there is a bzr process waiting around on
the other end to lock it for you.

In fact, you could loop the break-lock until it gives no output (since
break-lock won't complain if the lock isn't locked).

Just make sure that there really isn't anyone pushing to the directory.
Otherwise 2 people pushing to the same repository can intermix writes and
corrupt data.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHWaEMJdeBCYSNAAMRAsR2AKCEAGpvwphFJNB5yNtjQLRXgLf3dQCcD8p5
YAy7a9p+MX8z9siURoBbqds=
=ExtT
-----END PGP SIGNATURE-----