Corrupted repo? Full of unexpected changesets

[muxator]

Hi Kim,

I am not sure this is a good place for this sort of questions (it's a 
dev list).

Anyway, I used hg 4.3.3 to clone the repository you indicated.
Everything seems fine: maybe the repo is not an example of clean 
history, but nothing strange happened when cloning or verifying.

Is it possible that the problem is in your box?



$ hg clone https://hg.prosody.im/timber/
[...]
added 8111 changesets with 9350 changes to 386 files (+3 heads)
updating to bookmark @
212 files updated, 0 files merged, 0 files removed, 0 files unresolved

$ hg verify
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
386 files, 8111 changesets, 9350 total revisions






On 10/29/2017 02:23 AM, Kim Alvefur wrote:
> Hi,
>
> I've got a repo that, when running `hg verify`, produces a number of
> messages like:
>
>> rev 42 points to unexpected changeset 6074
> A tarball of the repo can be downloaded from
> <https://www.zash.se/upload/unexpected-changesets.tar.gz>
>
> It's a clone of <https://hg.prosody.im/timber/>.
>
> I'm not entirely sure what I have done to it. `hg debugupgraderepo` may
> have been involved, as well as hardlinking to other repos.
>
> Oddly enough, the problem appears to follow along when it is cloned.
>
> I don't consider recovery of this particulary important, I'm more
> interested in knowing how this could have happened and, if this can be
> traced down no a bug in hg, seeing that fixed.
>
>
>
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel