`bzr remove-tree` left almost empty .bzr/checkout, after that impossible to checkout tree again

[Alexander Belchenko]

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\MyCode\ACSD\AVR\Telemetry-Collector\TEST\ds1307_draft>bzr co
bzr: ERROR: Cannot lock LockDir(file:///C:/work/MyCode/ACSD/AVR/Telemetry-Collector/TEST/ds1307_draft/.bzr/checkout/lock): File
exists: u'C:/work/MyCode/ACSD/AVR/Telemetry-Collector/TEST/ds1307_draft/.bzr/checkout/lock': [Error 183] Cannot create a file when that file already exists: u'C:/work/MyCode/ACSD/AVR/Telemetry-Collector/TEST/ds1307_draft/.bzr/checkout/lock'

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.

[Jelmer Vernooij (jelmer)]

presumably "bzr break-lock" would also help here, followed by "bzr co" ?