add-5-a-day: Could not acquire lock

[Wousser]

Trying to submit a bug to 5-a-day, I got the following error.

wouter@wouter-laptop:~/bugs$ add-5-a-day 12345
Tree is up to date at revision 642.
Unable to obtain lock lp--1218277780:///lock
held by <email address hidden> on host vostok [process #27425]
locked 49 minutes, 28 seconds ago
Will continue to try until 16:33:01

bzr: ERROR: Could not acquire lock "(remote lock)"
bzr failed with error code 768

[Daniel Hahler (blueyed)]

This happens when the remote repository/branch(?) is locked. This can happen while there's a ssh password prompt waiting for input somewhere else.

[Daniel Holbach (dholbach)]

The locks we had (like the one above) were ages old and not just a few seconds. I think this might be related to recent problems with lpbzr. The obvious workaround is: everybody commits to their own branch - that'd make statistics a bit more tricky.

[Daniel Hahler (blueyed)]

I think for the statistics, you could just merge all existing branches into a master and then work with it the same way you're doing it currently.
There shouldn't really be merge conflicts, as longs as everybody is only editing her own files, but in case there is, just skip the branch and notify the branch owner.

JFI: I've locked the repo myself once for ~1 hour or so, just by "add-5-a-day $FOO" in a console and forgetting about it.. it was waiting for the ssh key passphrase, because I've not ssh-added it before.

[Daniel Holbach (dholbach)]

For the statistics where do I get the URLs of the branches from? How do I merge if there is no common ancestor? I'm sure we'll figure something out.

Could we programmatically call bzr break-lock if the lock is older than say 5 minutes?

[Daniel Holbach (dholbach)]

With version 0.23 this should be less of an issue, marking importance 'low':

  * five-a-day/parser.py, five-a-day/bzr.py: merged relevant portions of
    http://bazaar.launchpad.net/~blueyed/five-a-day/five-a-day-lazy-remote by
    Daniel Hahler <email address hidden>, now 5-a-day --add will only commit
    changes to the branch, if either
    - changes haven't been committed in the last hour or
    - --force (or -f) is supplied.

[Daniel Holbach (dholbach)]

Did you ever encounter the problem again?

[Wousser (wousser)]

Thanks for you response. I don't encounter the problem again.

On Tue, Jun 17, 2008 at 2:42 PM, Daniel Holbach <email address hidden>
wrote:

> Did you ever encounter the problem again?
>
> --
> add-5-a-day: Could not acquire lock
> https://bugs.launchpad.net/bugs/196635
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[kovax (kovax3)]

bzr break-lock lp.......etc

to fix probleme