Bug#928111: [pre-approval] unblock: icu/63.2-1
Control: tags -1 -moreinfo
On Mon, Jun 17, 2019 at 9:50 PM Paul Gevers <elbrus@debian.org> wrote:
> On 16-06-2019 11:20, László Böszörményi (GCS) wrote:
[The ICU 63.2 upstream release]
> > Last but not least fixed the startup slowness issue, changing a
> > function signature as well. While this is a public function, I guess
> > not meant to be used externally. It's an ABI break nevertheless
> > without a soname bump. The good thing is that it's only used by the V8
> > JavaScript engine (being in Chromium). Just for the record, this mean
> > chromium, nodejs and qtwebengine-opensource-src will need binNMUs once
> > I can upload this change to Sid.
>
> Do I understand correctly that what we are now getting with this version is:
>
> - Reiwa support
> - fix for the speed regression?
>
> Can you confirm that all the changes that I am seeing in your last diff
> (which were missing the debian/* changes by the way) are for those two
> issues?
You asked for the patched sources difference as I understood - not to
include noise with the patch changes under the debian directory.
Let me try to explain the current situation again. Current ICU version
in Sid is 63.2-2 which adds Reiwa support over the current version in
Buster.
The startup speed regression fix is _not_ present in this package
version. It would break the mentioned three source packages due to the
ABI change. The affected packages are binNMU-able, but the current
Chromium package is not ready to migrate to Buster and you can't
binNMU its Buster version. That's why it is only _planned_ for 63.2-3
which is _not_ yet uploaded.
Hope I could describe the current situation better.
Regards,
Laszlo/GCS
Reply to: