Control: tags -1 moreinfo Control: retitle -1 unblock: icu/63.2-2 Hi László, On 16-06-2019 11:20, László Böszörményi (GCS) wrote: >> Unfortunately, the state of chromium at this moment doesn't allow us to >> rebuild and have the package migrate to buster as chromium FTBFS on >> arm64 and the package is newer in unstable. You'll have to wait until >> that situation improves. > It improved but still not good. As it's irrelevant for now, let me > summarize the current status of ICU. > Unfortunately ICU 63.1 (which is in Buster already) have a startup > speed regression compared to previous versions. Chromium and > GraphicsMagick hit by this issue as I know, meaning these applications > start slower. > Then upstream released ICU 63.2 with three type of changes. First > security fixes that I've already backported to 63.1/Buster a while > ago. Then there's the Japanese new era "Reiwa" changes. This would be > nice to have for Buster. > 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? Paul
Attachment:
signature.asc
Description: OpenPGP digital signature