On Fri, 18 Mar 2022 at 17:38:43 +0100, László Böszörményi (GCS) wrote:
> At this point I remember only two packages that FTBFS
> with ICU 70.1 and I couldn't fix those. One is mozjs78 and the other
> is 0ad.
I think Ubuntu has already done this transition, so they might have
patches.
0ad bundles a copy of mozjs 78.6.0, so if we can fix mozjs78, then we can
probably also fix 0ad by applying the same patch.
If we can't fix it any other way, we can build those packages with
their vendored copy of ICU. firefox-esr (which is a superset of mozjs91)
already uses a vendored copy of ICU, so there's precedent.
Obviously all these copies of essentially the same codebase are quite
unfortunate, but mozjs and ICU seem to be sufficiently tightly-coupled
that perhaps using its vendored version of ICU, at least temporarily,
would be wiser than using the system copy?
On Fri, 18 Mar 2022 at 18:26:41 +0100, László Böszörményi (GCS) wrote:
> Speak of the devil. ICU 71.1 RC [1] just released. Final is expected
> in April (two-three weeks). Would you two mind if I package it and ask
> for testing of your packages (mozjs91 and nodejs) against it?
Speaking only for myself, I'm flexible about timings for this; but Ubuntu
has already done the ICU 70.1 transition and is currently using it for
their next LTS release, and 2-3 weeks is probably too late for them to
do another transition before their freeze deadline.
smcv
