`bzr remove-tree` left almost empty .bzr/checkout, after that impossible to checkout tree again
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
My co-worker used `bzr remove-tree` in order to pack his branch and send it over e-mail. Unfortunately, it seems remover-tree wasn't finished successfully, I suspect he had Bazaar Explorer opened. So, his packed branch after remove-tree still contained almost empty `checkout` directory with following directories:
lock/ -> empty
shelf/ -> empty
and file dirstate of zero bytes length.
When trying to recover the working tree with `bzr checkout` we got error:
C:\work\
bzr: ERROR: Cannot lock LockDir(
exists: u'C:/work/
I suspect this could be win32-specific problem of `remove-tree` itself.
Manually deleting .bzr/checkout directory fixes the problem and `bzr co` worked. But it's not obvious for less experienced users what to do.
tags: | added: check-for-breezy |
presumably "bzr break-lock" would also help here, followed by "bzr co" ?