Bug#894159: transition: icu
On Mon, Apr 23, 2018 at 11:31 PM Emilio Pozuelo Monfort <pochu@debian.org>
wrote:
> On 23/04/18 21:40, László Böszörményi (GCS) wrote:
> > I do agree and open to do an other compilation test of the dependent
> > packages with icu-config being available.
> Thanks. Let me know how that goes, and I'll ack this transition as soon
as possible.
OK, the fresh transition testing is the following.
Level 1:
I don't know how haskell-yi-rope directly related, but it builds with the
rest of the packages.
Level 1.5:
I choose this intermediate step to build both Boost1.62 and Boost1.63 as
well correctly.
Level 2:
dee FTBFS for an unrealated issue, #876594 [1].
libsimpleini fails only due to it needs library symbols update. Maintainer
is Cc-d.
pyicu FTBFS, seems unmaintained. Last upload was in 2016 and since then
there were seven upstream releases. Version 1.9.8+ builds fine with the new
ICU version. Maintainer also Cc-d, may I overtake it?
Level 3:
node-stringprep FTBFS for an unrelated issue, #895029 [2].
webkitgtk FTBFS, requested to be removed[3] due to unmaintained and many
security bugs. That's why I ignored it. Probably variable casting problems
is the FTBFS reason, see later.
Level 4:
cyrus-imapd FTBFS for an unrelated issue, #883951 [4].
haskell-blogliterately FTBFS for an unrelated issue, #897172 [5].
Level 5:
kbibtex FTBFS for an unrelated issue, #893538 [6].
qtwebengine-opensource-src is strange. Previously it built for me, even
built for the maintainers when previous package versions (5.10.1+dfsg-1 and
5.10.1+dfsg-2) were uploaded to experimental. Now it FTBFS due to GCC
being picky. Recent ICU (59.1+) named variable types to be consistent for
different architectures. That is, UChar defaults to char16_t but can be
uint16_t if the architecture / compiler requires that.
Probably newer GCC versions no longer do the automatic type casts. I had to
add them explicitly. No code change was needed. With my patch, this package
builds correctly again.
Cheers,
Laszlo/GCS
[1] https://bugs.debian.org/876594
[2] https://bugs.debian.org/895029
[3] https://bugs.debian.org/893863
[4] https://bugs.debian.org/883951
[5] https://bugs.debian.org/897172
[6] https://bugs.debian.org/893538
Reply to: