<a class="header-button" href="https://bugzilla.mozilla.org/home" title="Go to home page"> Bugzilla

Assignee

Comment 6

•

1 year ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: dbe553dd13b79a3c4821f203f3adca31fe71cc56
comm-central: 6985935c40cd4220f815f7bd28b43d4f95d19252

Updated

•

1 year ago

Keywords: checkin-needed-tb

Comment 7

•

1 year ago

Pushed by solange@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/ae1c6d898aa3
Synchronize vendored Rust libraries with mozilla-central. r=babolivier

Keywords: checkin-needed-tb

Assignee

Comment 8

•

1 year ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: a8a8cdb0966b3f9e6d533229b92e89d516335ce5
comm-central: faf461aa24f07a318ca7d84e79e2270f19e26155

•

1 year ago

Keywords: checkin-needed-tb

Comment 18

•

1 year ago

Pushed by ikey@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/46a93c486805
Synchronize vendored Rust libraries with mozilla-central. r=babolivier

Keywords: checkin-needed-tb

Assignee

Comment 19

•

1 year ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: 48ac42d415d3e0a736f64fe38783e455f072917b
comm-central: 57bbe45078e5efef5c2e601a843fda262de28fe4

•

1 year ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: 8ea0c0ea3c7c794cd475d0839f70a26ceb7ff58c
comm-central: 047030d893e8d48eb799711be08f54b6026703af

Updated

•

1 year ago

Keywords: checkin-needed-tb

•

1 year ago

Keywords: checkin-needed-tb

Comment 26

•

1 year ago

Pushed by ikey@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/15da731f2d26
Synchronize vendored Rust libraries with mozilla-central. r=mkmelin

Keywords: checkin-needed-tb

Assignee

Comment 27

•

1 year ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: 2356949f5c6d9a4f229d012051bac51b3eb83aec
comm-central: 0aa0923b7e837a0bab124a430c452b12ae6c6a84

Updated

•

1 year ago

Attachment #9388223 - Attachment is obsolete: true

•

1 year ago

Keywords: checkin-needed-tb

Comment 32

•

1 year ago

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/8f758628d3fa
Synchronize vendored Rust libraries with mozilla-central. r=ikey

Keywords: checkin-needed-tb

Assignee

Comment 33

•

1 year ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: c90923a84670e17105b275c5be4a3c2842cb248e
comm-central: c10fd45989174962b4b182ef6a6036a2adeceace

Updated

•

1 year ago

Keywords: checkin-needed-tb

Comment 34

•

1 year ago

Pushed by daniel@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/d8e5063a7e01
Synchronize vendored Rust libraries with mozilla-central. r=babolivier

Keywords: checkin-needed-tb

Assignee

Comment 35

•

1 year ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: 63e18d5ef9ecb56ee260694de696c442f0bd5670
comm-central: 19a8713205ecf36663ecf338b16df5bae47aa9d0

Updated

•

1 year ago

Keywords: checkin-needed-tb

Comment 36

•

1 year ago

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/549cbe35743b
Synchronize vendored Rust libraries with mozilla-central. r=babolivier

Keywords: checkin-needed-tb

Assignee

Comment 37

•

1 year ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: 099f52f30c39008328dfbc02ff824310e082a8da
comm-central: 8f79d9e50fc9003754c03100ab9aecaed22d4c0e

Ikey Doherty

Updated

•

1 year ago

Keywords: checkin-needed-tb

Comment 38

•

1 year ago

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/2b81c33e69a2
Synchronize vendored Rust libraries with mozilla-central. r=ikey

Keywords: checkin-needed-tb

Assignee

Comment 39

•

1 year ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: aded201f11ec90b8e11c59d1e399960785771fbd
comm-central: cd4e83a903af4e433da4bd4866797030dc64e16a

Updated

•

1 year ago

Keywords: checkin-needed-tb

Comment 40

•

1 year ago

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/9d1347d3c085
Synchronize vendored Rust libraries with mozilla-central. r=babolivier

Keywords: checkin-needed-tb

Assignee

Updated

•

1 year ago

Keywords: checkin-needed-tb

Comment 48

•

1 year ago

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/05f06005402b
Synchronize vendored Rust libraries with mozilla-central. r=mkmelin

Keywords: checkin-needed-tb

Assignee

Comment 49

•

1 year ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: ca250739126614322a325fededc713174a6ad565
comm-central: 9b38c8a16e5985d619709992c5425e568a92619c

Updated

•

1 year ago

Keywords: checkin-needed-tb

Comment 50

•

1 year ago

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/f955b4ec1294
Synchronize vendored Rust libraries with mozilla-central. r=mkmelin

Keywords: checkin-needed-tb

Assignee

•

11 months ago

Keywords: checkin-needed-tb

Comment 59

•

11 months ago

Pushed by martin@humanoids.be:
https://hg.mozilla.org/comm-central/rev/a4b5e564fa30
Synchronize vendored Rust libraries with mozilla-central. r=babolivier

Keywords: checkin-needed-tb

Assignee

Comment 60

•

11 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: cfb42711da4589f5ede0032644a6d577d66aa468
comm-central: a4b5e564fa308e5d1eabcd9fe0302a2315ce6f25

Updated

•

11 months ago

Keywords: checkin-needed-tb

Assignee

Comment 61

•

11 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: 1d9c4672f9f5ee5ec7faa0fdfcf2aa0f740da476
comm-central: a4b5e564fa308e5d1eabcd9fe0302a2315ce6f25

Comment 62

•

11 months ago

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/2d452779350c
Synchronize vendored Rust libraries with mozilla-central. r=mkmelin

Keywords: checkin-needed-tb

Assignee

Comment 63

•

11 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: f2360b4c9b8a110f0b1c40841a767a47da5b85be
comm-central: 36e10207ec5d2ca64819c32919a6c0b9bf75fa01

Updated

•

11 months ago

Keywords: checkin-needed-tb

Comment 64

•

11 months ago

Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/21f65331169f
Synchronize vendored Rust libraries with mozilla-central. r=mkmelin

Keywords: checkin-needed-tb

Assignee

Updated

•

11 months ago

Keywords: checkin-needed-tb

Comment 73

•

11 months ago

Pushed by john@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/bfefefe91c34
Synchronize vendored Rust libraries with mozilla-central. r=ikey

Keywords: checkin-needed-tb

Assignee

Comment 74

•

11 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: 036ac9a41b52b5af1836d103d3a7aefad37e2b87
comm-central: c837b0432a89063750e9388fd4259f03e4b8f930

Ikey Doherty

Updated

•

11 months ago

Keywords: checkin-needed-tb

Comment 75

•

11 months ago

Pushed by john@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/95623aba784c
Synchronize vendored Rust libraries with mozilla-central. r=aleca

Keywords: checkin-needed-tb

Assignee

Comment 76

•

11 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: 09eb10704814dc36a0879f664ea637ee40554fe5
comm-central: 311b7ba5a87f74d1805ea162fec1b2792c371db0

Updated

•

11 months ago

Keywords: checkin-needed-tb

Comment 77

•

11 months ago

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/dbed85730505
Synchronize vendored Rust libraries with mozilla-central. r=mkmelin

Keywords: checkin-needed-tb

Assignee

Comment 78

•

11 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: c715b86068059bd614e2bac57bba333b46b090e0
comm-central: ba70c39931ec4e9474f4350cb040317662c7daef

Comment 79

•

11 months ago

Pushed by thunderbird@calypsoblue.org: https://hg.mozilla.org/comm-central/rev/6b6e06894eb5 Synchronize vendored Rust libraries with mozilla-central. r=rjl

Assignee

Comment 80

•

11 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: ed724b89a2c25252a6eab99f0fa48f85f2523b66
comm-central: 3d7ce46c80c5cbb7cfdcab928e795babbedd7a35

Assignee

Comment 81

•

11 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers (obsolete) — Details

mozilla-central: ed724b89a2c25252a6eab99f0fa48f85f2523b66
comm-central: 3d7ce46c80c5cbb7cfdcab928e795babbedd7a35

Comment 93

•

•

10 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: d3307ce15a2e8d72b309c71e28226a07864e3bb2
comm-central: 445334850d02f3861dbb691e6ef6a0b84584071b

Updated

•

10 months ago

Keywords: checkin-needed-tb

Comment 118

•

10 months ago

Pushed by daniel@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/6e4c7fa5f637
Synchronize vendored Rust libraries with mozilla-central. r=babolivier

Keywords: checkin-needed-tb

Assignee

Updated

•

10 months ago

Keywords: checkin-needed-tb

Comment 128

•

•

9 months ago

Pushed by brendan@thunderbird.net: https://hg.mozilla.org/comm-central/rev/a63620f59465 Synchronize vendored Rust libraries with mozilla-central. r=babolivier

Comment 184

•

9 months ago

Just a question.
I have been creating C++ source code level patches under linux on a local machine.

Are we forever adding these updates to C-C tree?
(Given the nature it seems so.)

For the last couple of weeks, I have observed that when the C-C tree is a bit out of sync, I suspect we may get the
inconsistent rust dependency and |mach build| would fail and suggest to run |mach tb-rust vendor|.

But from the past several days of mess in my local repo,
(which is reported in https://groups.google.com/a/mozilla.org/g/dev-platform/c/MToavd6zYZk )
probably I should have NOT run |make tb-rust vendor| locally, but rather should have WAITED FOR
the patches posted here to land in the C-C tree.
And ONLY THEN, I probably should just |hg pull -u| although that means there will window of non-build on local machine which is very frustrating.

Can someone give an overview of what the ordinary patch contributor should do when one sees "Run |mach tb-rust vendor|" ?
This is a real pain for someone who tinkers with C++ source code.
Luckily artifact patch contributors, who don't need C++/rust compilation, won't be bothered at all.
If there is a simple guideline to change Cargo.toml in a bandage manner, based on a message shown by |mach build|, even before the official patch appears, that would be super.

With the latest patch posted 10 hours ago (?), the pristine M-C/C-C trees I have re-fetched finally seem to compile the untouched C-C tree without an issue. Things were rather much rougher on the weekend.
(But as I wonder at the beginning of this post, things will/may break when M-C portion gets updated.)
https://treeherder.mozilla.org/jobs?repo=try-comm-central&revision=db82151916fe73aeac38fe70868898f5d148a4f8

Comment 185

•

9 months ago

Pushed by geoff@darktrojan.net: https://hg.mozilla.org/comm-central/rev/e070c1ba5fd5 Synchronize vendored Rust libraries with mozilla-central. r=darktrojan

Assignee

Comment 186

•

9 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers (obsolete) — Details

mozilla-central: 22bab7a24384ad860900ddccc70b2e64f8ba35fc
comm-central: 597ecc8eb8a888270d915e44844db9d10819b795

Updated

•

9 months ago

Attachment #9409580 - Attachment is obsolete: true

Comment 187

•

9 months ago

I should have referred to the e-mails I sent to Maildev mailing list:
https://thunderbird.topicbox.com/groups/developers/T8ae4ae8c2c2bd959-M5a4649717a36accc9ac0729b?subscription_form=8c2eaa9a-c0eb-11e8-bb0b-59b48f05e7cf

I believe the above threads contain the kind of problems one may experience during local compilation/build.

I agree having two-layered hg repositories is not an ideal situation.
Having many source files pulled and managed from many git repositories inside the two-layered repositories compounds the situation. Trying to manage the situation using the already brittle two-layered repository is a crazy idea IMHO.
But I digress. There must be a host of rationals to make it a valid approach for M-C FF development.
It is the added C-C repository that does not play nice currently.

(In reply to ISHIKAWA, Chiaki from comment #184)

Just a question.
...

But from the past several days of mess in my local repo,
(which is reported in https://groups.google.com/a/mozilla.org/g/dev-platform/c/MToavd6zYZk )
probably I should have NOT run |make tb-rust vendor| locally, but rather should have WAITED FOR
the patches posted here to land in the C-C tree.
And ONLY THEN, I probably should just |hg pull -u| although that means there will window of non-build on local machine which is very frustrating.

The reason I thought I should not have run |mach tb-rust vendor| locally and |cargo update| is that
eventually, the action brought in changes to third_party/rust which the rust compiler and C++ compiler failed due to syntax errors (missing symbol name at compile time [obviously a mismatch between versions since renaming the symbol to a similarly named data type succeeded compilation]), and a very strange link time error, which showed stderr, fflush and a few other libc functions were missing from the link step of a command, which was quite puzzling since similar binaries under the same directory succeeded.

Anyway, finally I thought I can compile/build locally since I could submit a try-comm-central job from an unmodified C-C tree copy.
https://treeherder.mozilla.org/jobs?repo=try-comm-central&revision=db82151916fe73aeac38fe70868898f5d148a4f8

Again, when things got out of sync, it was a serious issue for only those who compile rust and C++/C code locally. I wasted a week because of the issues.
I am glad finally the trees are in a stable situation again. I just found out that my local build/compile succeeded.

Playing only with artifact parches should not be inconvenienced at all from what I observe on try-comm-central.

The message about }cargo update|: The following appeared a few times in the build log.

warning: Patch `any_all_workaround v0.1.0 (https://github.com/hsivonen/any_all_workaround?rev=7fb1b7034c9f172aade21ee1c8554e8d8a48af80#7fb1b703)` was not used in the crate graph.
Patch `backtrace v0.3.999 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/build/rust/backtrace)` was not used in the crate graph.
Patch `base64 v0.13.999 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/build/rust/base64)` was not used in the crate graph.
Patch `icu_capi v1.5.0 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/intl/icu_capi)` was not used in the crate graph.
Patch `indexmap v1.999.999 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/build/rust/indexmap)` was not used in the crate graph.
Patch `plist v1.3.1 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/third_party/rust/plist)` was not used in the crate graph.
Patch `terminal_size v0.3.999 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/build/rust/terminal_size)` was not used in the crate graph.
Patch `warp v0.3.6 (https://github.com/seanmonstar/warp?rev=9d081461ae1167eb321585ce424f4fef6cf0092b#9d081461)` was not used in the crate graph.
Patch `windows-sys v0.48.999 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/build/rust/windows-sys)` was not used in the crate graph.
Patch `zip v0.6.4 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/third_party/rust/zip)` was not used in the crate graph.
Check that the patched package version and available features are compatible
with the dependency requirements. If the patch has a different version from
what is locked in the Cargo.lock file, run `cargo update` to use the new
version. This may also occur with an optional dependency that is not enabled.
...

Comment 188

•

9 months ago

(In reply to ISHIKAWA, Chiaki from comment #187)
...

The message about }cargo update|: The following appeared a few times in the build log.

warning: Patch `any_all_workaround v0.1.0 (https://github.com/hsivonen/any_all_workaround?rev=7fb1b7034c9f172aade21ee1c8554e8d8a48af80#7fb1b703)` was not used in the crate graph.
Patch `backtrace v0.3.999 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/build/rust/backtrace)` was not used in the crate graph.
Patch `base64 v0.13.999 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/build/rust/base64)` was not used in the crate graph.
Patch `icu_capi v1.5.0 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/intl/icu_capi)` was not used in the crate graph.
Patch `indexmap v1.999.999 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/build/rust/indexmap)` was not used in the crate graph.
Patch `plist v1.3.1 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/third_party/rust/plist)` was not used in the crate graph.
Patch `terminal_size v0.3.999 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/build/rust/terminal_size)` was not used in the crate graph.
Patch `warp v0.3.6 (https://github.com/seanmonstar/warp?rev=9d081461ae1167eb321585ce424f4fef6cf0092b#9d081461)` was not used in the crate graph.
Patch `windows-sys v0.48.999 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/build/rust/windows-sys)` was not used in the crate graph.
Patch `zip v0.6.4 (/NEW-SSD/NREF-COMM-CENTRAL/mozilla/third_party/rust/zip)` was not used in the crate graph.
Check that the patched package version and available features are compatible
with the dependency requirements. If the patch has a different version from
what is locked in the Cargo.lock file, run `cargo update` to use the new
version. This may also occur with an optional dependency that is not enabled.
...

I forgot to mention that the warning was followed by the error:

error: the lock file /NEW-SSD/NREF-COMM-CENTRAL/mozilla/comm/rust/Cargo.lock needs to be updated but --frozen was passed to prevent this
If you want to try to generate the lock file without accessing the network, remove the --frozen flag and use --offline instead.

until I temporarily disabled the error (which I am not quite sure if the right thing to do) with the following patch
I think I NEED the following tweak to compile/build locally under Linux even with the latest tree.

# HG changeset patch
# User ISHIKAWA, Chiaki <ishikawa@yk.rim.or.jp>
# Parent  d80e4d0ca4db63de8b5c1efdf5a4a153b1b0686a
replace "-frozen" with "-offline"

diff --git a/config/makefiles/rust.mk b/config/makefiles/rust.mk
--- a/config/makefiles/rust.mk
+++ b/config/makefiles/rust.mk
@@ -18,18 +18,24 @@ cargo_build_flags = $(CARGOFLAGS)
 ifndef MOZ_DEBUG_RUST
 cargo_build_flags += --release
 endif
 
 # The Spidermonkey library can be built from a package tarball outside the
 # tree, so we want to let Cargo create lock files in this case. When built
 # within a tree, the Rust dependencies have been vendored in so Cargo won't
 # touch the lock file.
+
+# error: the lock file /NEW-SSD/NREF-COMM-CENTRAL/mozilla/Cargo.lock needs to be updated but --frozen was passed to prevent this
+# If you want to try to generate the lock file without accessing the
+# network, remove the --frozen flag and use --offline instead.
+
+
 ifndef JS_STANDALONE
-cargo_build_flags += --frozen
+cargo_build_flags += --offline
 endif
 
 cargo_build_flags += --manifest-path $(CARGO_FILE)
 ifdef BUILD_VERBOSE_LOG
 cargo_build_flags += -vv
 endif
 
 ifneq (,$(USE_CARGO_JSON_MESSAGE_FORMAT))

Comment 189

•

9 months ago

Pushed by geoff@darktrojan.net: https://hg.mozilla.org/comm-central/rev/fcf546831cdb Synchronize vendored Rust libraries with mozilla-central. r=darktrojan

Comment 190

•

9 months ago

(In reply to ISHIKAWA, Chiaki from comment #184)

Are we forever adding these updates to C-C tree?

Yes, unless we find a better solution.

To your question about how to avoid the pain:

for all work, as a starting point have m-c and c-c properly in sync
apply your wip patches
stay on that working branch as long as you need - don't pull in latest before you plan to rebase
every few days or so, pull in latest from both, and rebase your work to tip
(after pulling, I do hg rebase -s "draft()" -d "public()" - yeah, probably way harder with mq)

Comment 200

•

8 months ago

•

Edited

(In reply to Magnus Melin [:mkmelin] from comment #190)

(In reply to ISHIKAWA, Chiaki from comment #184)

Are we forever adding these updates to C-C tree?

Yes, unless we find a better solution.

Thank you for the pointer.

I think it took me about another week to have a stable local tree.

To your question about how to avoid the pain:

for all work, as a starting point have m-c and c-c properly in sync

The above actually was rather difficult initially.
The way M-C tree and C-C tree get updated definitely creates a window of inconsistency, and
I tended to get the unsynchronized trees unfortunately.

But now they seem to be rather stable.

HOWEVER, for anyone reading this bugzilla, I have to report that |mach build| complained
about the rust dependency inconsistencies one time, and the M-C and C-C trees have been updated, and it seemed that C-C tree had picked up the necessary modification already for a day or something like that.
This puzzled me for a while.
Then it hit me.
I did |mach bootstrap| and to my surprise, some binary packages used for compilation were updated.
THEN, the rust dependency issue was gone for this particular combination of M-C and C-C tree.
This point may need to borne in mind when someone builds binary locally (well I do under linux).

apply your wip patches

stay on that working branch as long as you need - don't pull in latest before you plan to rebase
The above is a good advice indeed.

every few days or so, pull in latest from both, and rebase your work to tip
The above is what I do now.

(after pulling, I do hg rebase -s "draft()" -d "public()" - yeah, probably way harder with mq)
I have to think about this.
But actually for MQ, too, the above upgrade policy of M-C and C-C tree works.
Except one point.
Since I apply very stringent compiler warning options, I had to modify some files to keep such warnings to be issued.(I even apply -Werror so that any such warning results in compile-time error.) This FORCES me to fix source file construct that issues compiler warning.
Now, it used to be that some C modules used by rust requires changes under M-C tree. But now that same modules under C-C
tree get used, I have to modify the source files under C-C tree.
BUT, the change is only necessary for local C-C compilation where I use very stringent warning/error options. These changes are not necessary for tryserver compilation.
I have to throw away the changes to the C source files under third party rust library (specifically glslopt) and the change
to ignore the checksum for the glsolopt module before submitting the changed tree for compilation to try-comm-central.
With this step, the compilation finally works rather well.

However, to be honest, due to the timezone difference probably, the compilation locally and eventually on try-comm-central was a hit and miss affair for about a couple of weeks.
But now I understand the issues, I decide to wait for a few hours (or eye the possibility that |mach bootstrap| might solve the issue)
when a dependency issues keeps me from building C-C TB locally.

This definitely damages local source tree very badly and I had to re-install the C-C tree and import my patches from backup.
The damages are

files under hg management get removed due to the changes in the rust packages,
new files which won't be under hg management are introduced, and
for some reason, completely mismatched source files were installed that resulted in compiler errors.
I sensed something bad when the last problem occurs and after checking the status of the repository with |hg status|,
I learned it the hard way.
So I repeat
N E V E R R U N |mach tb-rust vendor| or {cargo update| locally.
Trust the source repositories (and the dependency information updated therein) and if the build don't succeed locally, wait for a few hours or a day or two. :-(

7 months ago

Pushed by sean@thunderbird.net: https://hg.mozilla.org/comm-central/rev/2597795492df Synchronize vendored Rust libraries with mozilla-central. r=leftmostcat

Daniel Darnell [:dandarnell]

Assignee

Comment 231

•

•

6 months ago

Pushed by kaie@kuix.de: https://hg.mozilla.org/comm-central/rev/79a9fa3ab3cc Synchronize vendored Rust libraries with mozilla-central. r=ikey

Comment 280

•

6 months ago

bugherder uplift

Thunderbird 131.0b4:
https://hg.mozilla.org/releases/comm-beta/rev/c65585bb8785

status-thunderbird131: --- → fixed

Comment 281

•

6 months ago

Pushed by geoff@darktrojan.net: https://hg.mozilla.org/comm-central/rev/868dfc35eaf5 Synchronize vendored Rust libraries with mozilla-central. r=darktrojan

Daniel Darnell [:dandarnell]

Assignee

Comment 282

•

6 months ago

Attached file Bug 1878375 - Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers — Details

mozilla-central: 2990b799422bb25a82bba52fac2d55a77d652dfa
comm-central: 48ef842f4c6c8aa73afbb59bd9a1050535e208ff

Comment 283

•

6 months ago

•

2 months ago

Pushed by kaie@kuix.de: https://hg.mozilla.org/comm-central/rev/f8272f84c87c Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers

Comment 408

•

2 months ago

Pushed by kaie@kuix.de: https://hg.mozilla.org/comm-central/rev/73dacdba669c Synchronize vendored Rust libraries with mozilla-central. r=#thunderbird-reviewers