Bug#898820: libicu-dev is not Multi-Arch compatible
Hi Hugh, On Wed, Jan 2, 2019 at 11:15 AM Hugh McMaster wrote: > * 389-ds-base is pending upload. This is uploaded since then and migrated to Buster. > * yaz is in the NEW queue. As I see the current situation, it won't make into Buster. As you have commit access to the package tree, can update the current version in the archives? Cheers, Laszlo/GCS
Bug#898820: libicu-dev is not Multi-Arch compatible
389-ds-base has been uploaded to unstable. On Wed, 2 Jan 2019 at 21:11, Hugh McMaster wrote: > > Hi László, > > All of the packages you listed in message #15 are fixed or pending > upload. Most are fixed upstream as well. > > * 389-ds-base is pending upload. > * yaz is in the NEW queue. > * gnustep-base is patched to use pkg-config, although it is compiled > with --disable-icu-config, so > not actually affected. > > What is the next step? > > Hugh
Bug#898820: libicu-dev is not Multi-Arch compatible
On Mon, Nov 26, 2018 at 10:54 AM Hugh McMaster wrote: > On Monday, 26 November 2018 6:14 PM, László Böszörményi wrote: > > Please help these projects, convince them to update their ICU library > > detection bits. As soon as no project depends on icu-config presence, > > I will disable that and make libicu63 Multi-Arch: same. > > Is the list in message #15 still valid? Or do I need to do a rebuild of > reverse build-dependencies? Should still be the same with the self-evident changes: older PHP versions are removed, it's php7.3 now which needs fixing. Maybe pyicu is fixed, but I don't think the others got any update. If you want, I can recheck these in the afternoon. Laszlo/GCS
Bug#898820: libicu-dev is not Multi-Arch compatible
Hi Hugh, On Wed, Nov 21, 2018 at 9:45 PM Hugh McMaster wrote: > What help do you need to resolve this bug? We have been to this route. As noted, indeed icu-config is deprecated long time ago and ICU can be detected with pkg-config instead. Several big projects like PHP (just checked its upcoming release, version 7.3) still don't handle the missing icu-config. Please help these projects, convince them to update their ICU library detection bits. As soon as no project depends on icu-config presence, I will disable that and make libicu63 Multi-Arch: same. Regards, Laszlo/GCS
Bug#898820: libicu-dev is not Multi-Arch compatible
Hi László, What help do you need to resolve this bug? Hugh
Bug#898820: libicu-dev is not Multi-Arch compatible
I am unable to build Wine due to several packages being not multiarch, libicu-dev is one of them. Any hope of having it fixed in debian relatively soon?
Bug#898820: libicu-dev is not Multi-Arch compatible
Hi, On Wed, Aug 22, 2018 at 6:39 AM Helmut Grohne wrote: > On Wed, May 16, 2018 at 10:42:50AM +0200, Francois Gouget wrote: > > The lack of multi-arch support in libicu-dev also breaks multi-arch > > support in the following packages: fis-gtm-6.3-003a libboost-regex1.62-dev > > libcdr-dev libe-book-dev libharfbuzz-dev libical-dev libmspub-dev > > libvisio-dev libxslt1-dev. So the impact is quite wide ranging. > > icu-config is deprecated upstream already, but still used in a variety > of downstream packages including libreoffice, qtwebkit-opensource-src, > libxml2, chromium-browser and many more. The impact of removinig > icu-config has worse consequences. For the time being, fixing this is > impractical. > > On the other hand, this tells us how to fix the issue: Make packages > stop using icu-config. Use pkg-config icu instead. When you send > patches, I suggest that you add a "block 898820 by $yourbug" to track > progress. I did a full dependency rebuild in March / April if I remember correctly. I've a small patch (even if it's not always elegant) for the following packages (LibreOffice no longer needs a patch as I know) to use pkg-config with ICU: 389-adminutil 389-ds-base 389-dsgw an dee dwdiff frog gnustep-base grcompiler ibus-qt libfolia openttd open-vm-tools php7.0 php7.1 php7.2 pyicu ucto webkitgtk yaz Of course, needs to check if these are still up-to-date or not. I will try to do it this week and probably file the bugs. Regards, Laszlo/GCS
Bug#898820: libicu-dev is not Multi-Arch compatible
On Wed, May 16, 2018 at 10:42:50AM +0200, Francois Gouget wrote: > libicu-dev is not multi-arch aware, causing the i386 version to conflict > with the amd64 one which makes it impossible to install both. As a > result the /usr/lib/i386-linux-gnu/libicu*.so symbolic links are missing > so that developping 32 bit applications using this library is > impossible on a 64 bit system. This is correct. The problem here is that libicu-dev ships icu-config. The behaviour of icu-config is architecture-dependent, but its path is not. There is no way to have it behave correctly for two architectures simultaneously. As long as icu-config is shipped, it cannot be coinstalled. That puts us between a rock and a hard place. > The lack of multi-arch support in libicu-dev also breaks multi-arch > support in the following packages: fis-gtm-6.3-003a libboost-regex1.62-dev > libcdr-dev libe-book-dev libharfbuzz-dev libical-dev libmspub-dev > libvisio-dev libxslt1-dev. So the impact is quite wide ranging. icu-config is deprecated upstream already, but still used in a variety of downstream packages including libreoffice, qtwebkit-opensource-src, libxml2, chromium-browser and many more. The impact of removinig icu-config has worse consequences. For the time being, fixing this is impractical. On the other hand, this tells us how to fix the issue: Make packages stop using icu-config. Use pkg-config icu instead. When you send patches, I suggest that you add a "block 898820 by $yourbug" to track progress. Another way to make a dent is tracking the size of the problem: Perform an archive rebuild with icu-config removed and diff against a regular archive rebuild. That'll tell us which packages need fixing. One could use sbuild --starting-build-commands="rm /usr/bin/icu-config" to do that. Thanks for your help Helmut
Bug#898820: libicu-dev is not Multi-Arch compatible
Package: libicu-dev Version: 57.1-9 Severity: normal Dear Maintainer, libicu-dev is not multi-arch aware, causing the i386 version to conflict with the amd64 one which makes it impossible to install both. As a result the /usr/lib/i386-linux-gnu/libicu*.so symbolic links are missing so that developping 32 bit applications using this library is impossible on a 64 bit system. In turn this impacts Wine development as it needs to support both 32 and 64 bit Windows applications and needs libxml2-dev for that. libxml2-dev itself is multi-arch same but it depends on libicu-dev and thus it's impossible to install both versions of libxml2-dev at the same time. The lack of multi-arch support in libicu-dev also breaks multi-arch support in the following packages: fis-gtm-6.3-003a libboost-regex1.62-dev libcdr-dev libe-book-dev libharfbuzz-dev libical-dev libmspub-dev libvisio-dev libxslt1-dev. So the impact is quite wide ranging. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libicu-dev depends on: ii icu-devtools 57.1-9 ii libc6-dev [libc-dev] 2.27-3 ii libicu57 57.1-9 ii libstdc++-5-dev [libstdc++-dev] 5.4.1-4 ii libstdc++-6-dev [libstdc++-dev] 6.4.0-12 ii libstdc++-7-dev [libstdc++-dev] 7.3.0-17 libicu-dev recommends no packages. Versions of packages libicu-dev suggests: pn icu-doc -- no debconf information
