![]() Try to add more content to the post 7 years, 5 months ago In my case (TortoiseHg V2.9.2 with Mercurial 2.7.2), the file name was "wlock" instead of "lock" and it was placed in the ".hg" directory, not in ".hg/store". hg/? When you say that the repositories “work”, doesn’t running hg up in one put the dirstate out of sync in the other-or does mercurial do something special to support this? 7 years, 6 months ago Welcome to Stackoverflow. 7 years, 6 months ago Doesn’t hg track dirstate in. It was my first time using the repository in several weeks, so I don't remember what could have left it in that state. Glad I'm not the only one! 7 years, 11 months ago FWIW it just happened to me on Ubuntu. 9 years, 3 months ago Wow, I also had a bluescreen while committing and got the same error. hg/wlock I had no idea what the issue was 9 years, 3 months ago Just a note for to say that running hg recover does not work unless you remove the lock first. 9 years, 11 months ago Many thanks - after removing. 10 years, 9 months ago hg recover should be run after a broken locking situation. Not sure, but you may be able to run $ hg recover without deleting the lockfile and it'll do it for you. Then I had to run $ hg recover to clear out the existing journal (& commit message) which I ctrl+c'ed. It was a symlink on 'nix to the current server:pid. 11 years, 5 months ago This was the case for me. I am surprised that a symlinked REP-ROOT/.hg works at all, although it seems to except for this push.ġ 10 years, 2 months ago Related Topics mercurial Comments 12 years, 6 months ago My problem had nothing to do with cloning or BSOD's but for me, I deleted the. I do understand, however, how somebody coming to Mercurial from another VCS might want this (Perforce does, although not a DVCS the Bazaar DVCS reportedly can do so). Mercurial does not understand the concept of two workspaces sharing the same repository. This is NOT a good thing to do with Mercurial. hg trees shared by symlink: A/.hg -symlinked-to-> B/.hg It turns out that the two workspaces, let's call them A and B, had. It turns out that the "hg push" was hanging waiting for a lock held by itself (or possibly a subprocess, I did not investigate further). When I went to the target of the push, and executed hg pull, no problem.Įventually I realized that the process ID on the hg push was lock waiting message was changing each time. But the lockfile was deleted when the hg command was killed. hg/store/lock while the command was hung, it existed. When I killed the hung hg command I could see no. Today I got the "waiting for lock on repository" on an hg push command. Mentioning in case someone other than me runs into it. I do not expect this to be a winning answer, but it is a fairly unusual situation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |