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

[John Arbash Meinel]

Nicholas Allen wrote:
> 
>> 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".
>>   
> I didn't get any prompt.
>> 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.
>>   
> 
> I did it in the branch that I was originally pulling from and then I ran
> bzr break-lock without specifying an argument.
> 

Well, there are still a few things we could check. Like:

Is there a .bzr/repository/lock/held directory? (And
.bzr/branch/lock/held, and .bzr/checkout/lock/held).

If we have to force it, you can just delete those directories, and it
breaks the locks. But I'd really like to figure out why bzr is hanging
first, so we can avoid running into this in the future.

Also, did you hit ^C more than 1 time? In general, we cleanup locks as
we are exiting, but sometimes it can take long enough that a second ^C
will kill it during cleanup. (I run into this more when I'm over a slow
SSH connection)

It might be nice if we printed: "^C caught, cleaning up locks", or
something like that. As is, you can hit ^C, and it seems like nothing
has happened.

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/70cf3af8/attachment.pgp