How do I fix this corruption (abort: when running status)?

[Chris Green]

On Sun, Jan 01, 2023 at 01:56:22PM -0500, Scott Palmer wrote:
>    On Jan 1, 2023, at 10:28 AM, Chris Green <cl at isbd.net> wrote:
> 
>      On Sun, Jan 01, 2023 at 02:53:29PM +0000, Chris Green wrote:
> 
>      On Sun, Jan 01, 2023 at 02:30:39PM +0000, Chris Green wrote:
> 
>      I have somehow managed to confuse my mercurial repository, when I
>      run
>      'hg status' I see:-
>         chris$ hg status
>         abort:
>      data/lib/bash/syncssh at a7caf35cd23f97636dfc1ec6f45f07c92e64a8cb:
>         no match found
>         chris$
>      I don't quite know how this happened, but how do I fix it?
> 
>      Further to this verify says:-
>         chris$ hg verify
>         checking changesets
>         checking manifests
>         crosschecking files in changesets and manifests
>         checking files
>          .ssh/config@?: rev 26 points to unexpected changeset 690
>          (expected )
>          warning: revlog 'data/lib/bash/syncssh.i' not in fncache!
>          755: empty or missing lib/bash/syncssh
>          lib/bash/syncssh at 755: manifest refers to unknown revision
>      a7caf35cd23f
>         checked 757 changesets with 2317 changes to 1376 files
>         2 warnings encountered!
>         hint: run "hg debugrebuildfncache" to recover from corrupt
>      fncache
>         3 integrity errors encountered!
>         (first damaged changeset appears to be 755)
> 
>      Well I've fixed it now, 'hg clone -r 754' and copy the result back
>      over the original repository, only two minor changes to redo so that
>      wasn't too bad!
> 
>    Did you try what the output of “hg verify” suggested?
> 
>    -> hint: run "hg debugrebuildfncache" to recover from corrupt fncache
> 
>    Just wondering if that didn’t work and that is why you did what you
>    did.
> 
Yes, I did try that and it did nothing useful at all.

-- 
Chris Green