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

[Nicholas Allen]

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