Mercurial push error

Brendan Cully brendan at kublai.com
Sat Jul 28 16:38:30 CDT 2007


On Saturday, 28 July 2007 at 08:11, Norman Walsh wrote:
> I have a mercurial repository that I've been using for a while.
> Everything seemed to work fine. Then I made a bunch of edits and
> issued a push. The push took tens of minutes if not an hour or more
> and finally failed:
> 
> ~$ hg --verbose push
> running ssh user at password "hg -R repository/path/name serve --stdio"
> pushing to ssh://user@password/repository/path/name
> searching for changes
> 19 changesets found
...
> remote:   File "/home/ndw/lib/python/mercurial/transaction.py", line 23, in __init__
> remote:     raise AssertionError(_("journal already exists - run hg recover"))
> remote: AssertionError: journal already exists - run hg recover
> $ hg recover
> no interrupted transaction available

The error is on the remote repository, so you'd have to run recover
there (probably by sshing to the remote host).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20070728/1eb7bad9/attachment.pgp 


More information about the Mercurial mailing list