Bug#912853: transition: icu
On Mon, Nov 12, 2018 at 4:05 PM Emilio Pozuelo Monfort <pochu@debian.org> wrote:
> On 11/11/2018 11:24, László Böszörményi (GCS) wrote:
> > On Sun, Nov 4, 2018 at 4:45 PM Laszlo Boszormenyi (GCS) <gcs@debian.org> wrote:
> >> I'd like to upload ICU 63.1 which was recently released for Buster.
> > I still miss the last three packages rebuilt, but I don't expect any
> > problems with those.
> > First, my methodology was to build the related packages both on i386
> > and amd64 (32 and 64 bit) to detect all possible problems in advance.
> > If a package failed due to ICU, I've patched it. If the reason was not
> > clear, rebuilt the package for Sid to check that result as well.
> > The order of rebuilds was harfbuzz -> boost1.67 -> make boost-defaults
> > point to it, then all other packages.
> Please go ahead with this. I will ack the boost transition once this is built.
Small update and a problem I might caused. ICU needs to be
bootstrapped via icu-le-hb. But the latter build depends on
src:harfbuzz which should have been binNMUed with the new ICU (63.1-3)
package version. The only package that can be affected over icu-le-hb
itself is openttd.
I've filed bugs for the ICU update request with the proposed patches.
Only sword is updated at the time of writing and it's own transition
with bibletime and xiphos said to be ongoing.
It is said that nodejs will upload its new major upstream release
which handles this ICU transition as soon as it's accepted from the
NEW queue and built fine for experimental.
The libkiwix maintainer also choose to use the new upstream release
for the transition, but it will need its zimlib build dependency
updated, which sits in the NEW queue as well.
Cheers,
Laszlo/GCS
Reply to: