Bugzilla

Hi,

Is there any chance that the earlier version of hg in my case 5.6.1 
regards a freshly fetched M-C tree to contain a local change or something?
After I updated M-C tree this morning
I cannot apply local MQUEUE (I know it is not recommended.) any more.
It says 
abort: local changes found
|hg diff| shows nothing.
Just for experimentation, I issue
|hg qnew temp| to take care of this phantom local change.
BUT, the next time I qpop the local change stored in |temp| patch, and they try to qpush this again,
hg complains 
abort: local changes found
There SHOULD NOT BE a local change after all and so something is wrong with the repo.

Oh well, either this bug affects the repository subtly with older |hg| command,  or I somehow messed up my repository by
running |hg pull -u| this morning.

Any ideas?

TIA

Hi,

Is there any chance that the earlier version of hg (in my case 5.6.1) 
regards a freshly fetched M-C tree to contain a local change or something due to the issues discussed here?
After I updated M-C tree this morning
I cannot apply local MQUEUE (I know it is not recommended.) any more.
It says 
abort: local changes found
|hg diff| shows nothing.
Just for experimentation, I issue
|hg qnew temp| to take care of this phantom local change.
BUT, the next time I qpop the local change stored in |temp| patch, and they try to qpush this again,
hg complains 
abort: local changes found
There SHOULD NOT BE a local change after all and so something is wrong with the repo.

Oh well, either this bug affects the repository subtly with older |hg| command,  or I somehow messed up my repository by
running |hg pull -u| this morning.

Any ideas?

TIA
PS:
```
The version of M-C I have is this.
 hg log | head -100
changeset:   586141:a8a4dfcadce5
tag:         tip
fxtree:      central
user:        Marian-Vasile Laza <mlaza@mozilla.com>
date:        Tue Jul 20 16:33:08 2021 +0300
summary:     Backed out 11 changesets (bug 1721333) for causing crashtest/mochitest assertion failures on NativeObject.h. CLOSED TREE
...

```