Mercurial push error

[Matt Mackall]

On Sat, Aug 04, 2007 at 07:41:50AM -0400, Norman Walsh wrote:
> / Matt Mackall <mpm at selenic.com> was heard to say:
> | On Sat, Jul 28, 2007 at 05:19:38PM -0400, Norman Walsh wrote:
> |> / Matt Mackall <mpm at selenic.com> was heard to say:
> |> | So it looks like someone (possibly you?) tried to push, and their
> |> | session got killed. Somehow Mercurial died without releasing the lock
> |> | and the transaction (this might happen if it gets OOM-killed or
> |> | similar). Your session eventually noticed the lock was stale and
> |> | claimed it, only to discover the aborted transaction.
> |> 
> |> How can I fix this so I can finish the push?
> |
> | It said:
> |
> | remote: AssertionError: journal already exists - run hg recover
> | ^^^^^^
> |
> | You need to run recover on the remote repo.
> 
> Ok. That seemed to help.
> 
> I login to the remote location, run hg recover, it rolls back.
> I run hg verify on the remote location and hg verify on the
> local location, all seems ok.

Did the remote repo have a sensible number of changesets reported by verify?

> I run
> 
> $ hg push
> pushing to ssh://user@host/path/to/hg/repos/home
> searching for changes
> remote: adding changesets
> remote: adding manifests
> remote: adding file changes

There should have been a line here about how many changes were sent.
Is this the complete message?

> $ hg verify
> checking changesets
> checking manifests
> crosschecking files in changesets and manifests
> checking files
> 2199 files, 24 changesets, 2390 total revisions
> 
> So far so good. Now I log back into the remote location
> 
> e$ hg verify
> checking changesets
> checking manifests
> bad manifest link (1) at revision 1

That's bad. Manifest revision 1 (ie the 2nd) says it belongs to
changeset 1, which doesn't exist.

Can you tell us what versions you're running and on what systems and
give us a directory listing of .hg and .hg/store on remote?

-- 
Mathematics is the supreme nostalgia of our time.