Interrupting pull with ctrl-C left stale locks that cannot be removed - even with bzr break-lock

[John Arbash Meinel]

Nicholas Allen wrote:
> Hi,
> 
> 
> I submitted this as a bug report already but just wondered if there is
> anything I can do in the meantime to fix this (ie is there a workaround?)
> 
> I was pulling a lot of revisions (about 1000) and half way through
> decided to stop the operation by Ctrl-C signal. The pull stopped as
> expected but then when I tried to resume it it said that a lock was
> still owned. So the original pull left a stale lock on the branch. I
> then decided to use bzr break-lock command to remove the locks as I knew
> the process has ended. However, bzr break-lock just hung and didn't do
> anything and the locks were left in place.
> 
> bzr info shows that the working tree, branch and repository are all
> locked. Now there is no way to use bzr with any branches in the entire
> repository as I cannot remove the locks.
> 
> Thanks,
> 
> Nick

Something seems really weird here. I'd be happy to help figure out what
is going on.

My best guess is something is holding the files open, and something is
causing us to hang when we go to peak to see who is holding the lock (we
prompt the user to let them verify that they are breaking the lock they
think they are breaking).

Or did you get the prompt, but it hung when you said "y".

Also, 'bzr break-lock' takes a location to unlock. Just as a check I'd
like to make sure you are breaking the right lock.

John
=:->


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20061031/05ce2079/attachment.pgp