I am developing TB patches locally on my linux PC.
Have anyone noticed mozilla/Cargo.lock seems to be in mercurial
repository and that it got updated
during development?
That is, as far as *I* am concerned, I never tough it directly.
But, it seems |mach clobber|, |mach configure|, |mach build| and other
|mach| invocations and the subsequent commands invoked within during
configure and compilation/build seemed to
change the file, mozilla/Cargo.lock. And during local hg update
(applying my patches, etc.), hg commands suddenly states
that there is a local diff and refresh my repository before proceeding.
Surprised, I check what changed. The changed file is Cargo.lock.
This happened twice over the weekend.
(I updated the source tree from the M-C and C-C repository a few times.
Each time the update worked OK. Only after a compilation and I tried to
apply my local patch, this happened. My using hg MQUEE feature should
not be a problem, though...)
The changes I noticed seem to be just the relocations of version
information of some tools/packages in different part of Cargo.lock.
(Simple deletion/addition of same block in different parts of the file.)
This is so strange, and I wonder if there is something wrong with my setup.
I thought this is the first time it happened on my PC, but a close check
of local patches revealed
something like this happened last August (Aug. 2019). Back then, I was
trying very hard to accommodate the source tree layout change (C-C now
having become the subtree of ./mozilla as mozilla/comm, and there were
many local patches and locally crafted scripts I needed to update and
it seems that I simply accepted Cargo.lock change as part of the big
tree layout and never bothered about it until today.)
Again, has anyone seen Cargo.lock being modified without direct user
intervention on their PC?
TIA
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
