tags:

views:

2768

answers:

4

Got a bluescreen in windows while cloning a mercurial repository.

After reboot, I now get this message for almost all hg commands:

c:\src>hg commit waiting for lock on repository c:\src\McVrsServer held by '\x00\x00\x00\x00\x00\ x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' interrupted!

Google is no help.

Any tips?

+10  A: 

This seems to resolve it, but don't know if it is safe:

Delete the repository file: .hg/store/lock

jm
My problem had nothing to do with cloning or BSOD's but for me, I deleted the .hg/wlock file to clear up the lock.
luckyllama
Yeah, I think that is what you need to do if your system is stuck with: "hg commit waiting for lock on repository"
jm
A: 

Not to punt here, but you might just ask around in the Mercurial IRC channel - #mercurial on irc.freenode.net.

pc1oad1etter
+2  A: 

If the locked repo was the original, I can't imagine it was modifying it to clone it, so it was only preventing you from changing it in the middle and messing up the clone. It should be fine after removing the lock.

The new cloned copy (if it was a local clone) could be in any sort of malformed state, though, so you should throw it out and start it over. (If it was a remote clone, I would hope it failed and already threw out the incomplete copy.)

markpasc
+5  A: 

Removing .hg/wlock (also) works.

Tiago Matos