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

[Wouter van Heyst]

On Tue, Oct 31, 2006 at 05:48:01PM +0100, 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.

From, not to?

Wouter van Heyst