Lock prevents from pushing in local mercurial repo

Question

Im trying to use mercurial for a project that will be developed on some disconnected PCs. I managed to setup the initial repo, and commit. But when I try to push, I get this message:

D:\work\havana2059-dvcs>hg push
pushing to D:\work\havana2059-dvcs
searching for changes
no changes found
waiting for lock on repository D:\work\havana2059-dvcs held by 'serenity:4816'

I have to interrupt it, because it simply stays there. How can I solve this?

Possible duplicate of [Mercurial stuck "waiting for lock"](http://stackoverflow.com/questions/12865/mercurial-stuck-waiting-for-lock) — marco.m, Feb 05 '17 at 15:59

score 2 · Answer 1 · edited May 23 '17 at 11:45

2

if you are sure it is supposed to be unlocked, then proceed to manually delete the lock file see Mercurial stuck "waiting for lock"

edited May 23 '17 at 11:45

Community

1
1

answered Feb 03 '17 at 16:04

arhak

2,282
1
22
37

The lock file is created when I run hg push. It dissapears when I interrupt the process. So, seems that push cant recognize its own lock. – user2929416 Feb 06 '17 at 15:49
did you see comment regarding `.hg/wlock`? – arhak Feb 07 '17 at 01:33
also consider `hg debuglock` for troubleshooting – arhak Feb 07 '17 at 01:36
a weird symlink situation at http://stackoverflow.com/questions/12865/mercurial-stuck-waiting-for-lock#25089553 – arhak Feb 07 '17 at 01:42

Lock prevents from pushing in local mercurial repo

1 Answers1