Hi Paul, On Sat, Jun 8, 2019 at 9:57 PM Paul Gevers <[email protected]> wrote: > On Sun, 5 May 2019 18:40:51 +0200 > =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= <[email protected]> wrote: > > Chromium is a bit bigger than me, but as I've experienced it's one of > > its pre-checks with an assert. As the size of the Unicode set is now > > bigger due to the addition of the new Japanese era it fails. Call it a > > lame check, but I tested this case vice-versa: built Chromium with ICU > > 63.2, then installed it with ICU 63.1 and it doesn't fail but working > > normally. > > Did you file a bug against chromium already about this? They should > improve the test to not fail like this in the future. If you haven't > done so, please file the bug ASAP. Nope, unfortunately ICU 63.2 breaks other things as well. I'm trying to find a solution for all the things, but couldn't finish it yet. I'm going to ping you again when I've a solution.
> On top of that, your package will have to add a versioned Breaks on the > latest chromium that is built against the current version of icu. This > has to be set when the package can be uploaded to unstable. Now is not > the time yet, see below. I know unfortunately. I'll revisit this again when I've an updated ICU package (first for experimental of course). > 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. While I think binNMU can be done for testing as well, I know that would make things more complicated. Chromium is a big beast, kudos to Michael Gilbert for maintaining that. Cheers, Laszlo/GCS
