"waiting for lock on repository"

[Sam's Lists]

Great.  That's what I figured.  Just wanted to make sure that I didn't have
to role anything back or revert anything from the last operation.  :)

Thanks


On Tue, Mar 31, 2009 at 5:38 PM, Benoit Boissinot <
benoit.boissinot at ens-lyon.org> wrote:

> On Tue, Mar 31, 2009 at 05:31:53PM -0700, Sam's Lists wrote:
> > Hi...
> >
> > Yesterday I had some network issues, and an operation disconnected
> halfway
> > through.
> >
> > Now when I do a: hg commit -m "fun"
> >
> > I get:
> > waiting for lock on repository /home/me/dev_branch/ws held by
> 'pepper:9149'
> > abort: repository /home/me/dev_branch/ws: timed out waiting for lock held
> by
> > pepper:9149
> >
> > There is no process (anymore) on pepper actually doing anything.
> >
> > How do I safely remove the lock?
>
> There should be a file (actually symlink) named lock inside the .hg,
> just remove it (if you're sure no actual processes are running).
> >
> > This question has been asked several times before on the web, but never
> > definitively answered (as far as I can tell), so it will be great to get
> an
> > answer for everyone.
> >
> > See:
> >
> http://stackoverflow.com/questions/12865/mercurial-stuck-waiting-for-lock/13205
> > http://www.nabble.com/Error:-timed-out-waiting-for-lock-td13259548.html
> > http://markmail.org/message/kuiy2uwuyhoo62jy
> >
>
> regards,
>
> Benoit
>
> --
> :wq
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090331/d35b24bf/attachment.htm