How to fix (fairly minor) error reported by verify?

[Chris Green]

How do I fix this:-

chris$ hg verify
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
clearMuttHtml@?: rev 0 points to unexpected changeset 135
(expected 134 137)
***@135: 1247b8363d74 not in manifests
427 files, 163 changesets, 530 total revisions
1 warnings encountered!
2 integrity errors encountered!
(first damaged changeset appears to be 135)
chris$

... or do I even need to worry about it?

[Adrian Klaver]

Post by Chris Green
How do I fix this:-
chris$ hg verify
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
(expected 134 137)
427 files, 163 changesets, 530 total revisions
1 warnings encountered!
2 integrity errors encountered!
(first damaged changeset appears to be 135)
chris$
... or do I even need to worry about it?

I would worry about the part:

clearMuttHtml@?: rev 0 points to unexpected changeset 135
(expected 134 137)
***@135: 1247b8363d74 not in manifests

I have never seen that in my repos, so unfortunately I do not have a
solution at hand. For those that might the following would be useful:

1) hg version(s) in play.

2) OS(es) in play

3) Repo history, e.g. was it cloned, have the changesets been moved back
and forth.

[Chris Green]

Post by Chris Green

Post by Chris Green
How do I fix this:-
chris$ hg verify
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
(expected 134 137)
427 files, 163 changesets, 530 total revisions
1 warnings encountered!
2 integrity errors encountered!
(first damaged changeset appears to be 135)
chris$
... or do I even need to worry about it?

(expected 134 137)
I have never seen that in my repos, so unfortunately I do not have a
1) hg version(s) in play.

Mercurial Distributed SCM (version 4.5.3)

Post by Chris Green
2) OS(es) in play

All Ubuntu linux (16.04 and 18.04)

Post by Chris Green
3) Repo history, e.g. was it cloned, have the changesets been moved back and
forth.

It's a fairly old repository, some years old, but had a major
re-organisation and increase in size just recently. I *think* the
above error probably appeared recently but I can't be totally sure.
There have been a lot of file movements within the repository recently
as I rearranged things and then changed my mind and did it again!

[Augie Fackler]

Post by Chris Green
(expected 134 137)

This is linkrev corruption. I’m not sure what the state of the art is in correcting it - *maybe* using `hg convert` to replay the revisions into a new repository.
This is harmless - you have an excess revision of sendCamPics in your repository that nothing references. It’s wasting a little disk space, but nothing more (if I’m remembering it correctly.)