Multiple Changesets Without Ancestors

[Adrian Buehlmann]

On 2015-05-10 12:18, Lasse Kliemann wrote:
> After some stress-testing (automated change of files, commit, pull,
> push, merge, ...) my test repos shows a couple of changesets that have
> no ancestors (parent is -1).
> 
> 'hg verify' runs fine.

Which is expected.

> Questions:
> 
> 1.) This should not happen, or did I miss something?

This can happen, for example, if you do a 'pull -f' from a unrelated
repository. See "hg help pull".

Normally, this is not used. As it happens, the Mercurial repository
itself has two roots:

    $ hg log -q -r "roots(::.)"
    0:9117c6561b0b
    2364:f368a1c302d5

(see "hg help revsets")

> 2.) How can the situation be diagnosed further?

Think twice before using 'pull -f' ?

> Of course, the repo is not important to me (just dummy data), but I'm
> apprehensive that something similar might happen in a production repos,
> and then I need to know what to do.
> 
> Ok... just now I see, the hg I use on some of the systems is
> ancient. It's 2.8.2, still shipped with Ubuntu in 2015!
> Maybe that's the problem?

That's likely completely unrelated.