What does this abort: error mean?

[Chris Green]

On Tue, Jul 27, 2021 at 09:49:56AM +0100, Chris Green wrote:
> I just ran 'hg status' and got the following error:-
> 
>     chris at t470$ hg status
>     abort: data/bison/bin/a.i at 2081505f56cc: no match found!
>     chris at t470$ 
> 
> I have been messing around with things recently so it's probably my
> fault, but how do I sort it out?
> 
I just tried running 'hg verify':-

    chris$ hg verify
    checking changesets
    checking manifests
    crosschecking files in changesets and manifests
    checking files
     warning: revlog 'data/bison/.bash_logout.i' not in fncache!
     467: empty or missing bison/.bash_logout
     bison/.bash_logout at 467: manifest refers to unknown revision ad95c02e71de
     warning: revlog 'data/bison/.bashrc.i' not in fncache!
     467: empty or missing bison/.bashrc
     bison/.bashrc at 467: manifest refers to unknown revision 6010ebf5b232
     warning: revlog 'data/bison/.termux/termux.properties.i' not in fncache!
     467: empty or missing bison/.termux/termux.properties
     bison/.termux/termux.properties at 467: manifest refers to unknown revision 6ef37c6c84d3
     warning: revlog 'data/bison/bin/a.i' not in fncache!
     467: empty or missing bison/bin/a
     bison/bin/a at 467: manifest refers to unknown revision 2081505f56cc
    checked 468 changesets with 1058 changes to 680 files
    4 warnings encountered!
    hint: run "hg debugrebuildfncache" to recover from corrupt fncache
    8 integrity errors encountered!
    (first damaged changeset appears to be 467)

So I ran the recommeded command:-

    chris$ hg debugrebuildfncache
    removing data/bison/.bash_logout.i
    removing data/bison/.bashrc.i
    removing data/bison/.termux/termux.properties.i
    removing data/bison/bin/a.i
    0 items added, 4 removed from fncache


However I still get the error:-

    chris$ hg status
    abort: data/bison/bin/a.i at 2081505f56cc: no match found!


There's very little in the bison subdirectory, I could get rid of it all and start
again without much trouble, but I need to clear that error in some way that won't
break things.




-- 
Chris Green