Hi, Am Di, 11 Jun 2024 08:19:54 +0200 schrieb Mathieu Malaterre <ma...@debian.org>:
> Julian, > > On Tue, Jun 11, 2024 at 1:06 AM Jeremy Bícha > <jeremy.bi...@canonical.com> wrote: > > > > Source: jpeg-xl > > Version: 0.9.2-6 > > Severity: serious > > Tags: experimental > > > > jpeg-xl in experimental has autopkgtests that are failing on all > > architectures except for amd64. > > > > Specifically, the problem is that debian/libjxl-gdk-pixbuf.postinst > > and debian/libjxl-gdk-pixbuf.postrm have hardcoded the amd64 > > architecture which means that libjxl-gdk-pixbuf is uninstallable on > > architectures other than amd64. > > > > https://ci.debian.net/packages/j/jpeg-xl/unstable/arm64/ > > > > https://salsa.debian.org/debian-phototools-team/libjxl/-/blob/debian/experimental/debian/libjxl-gdk-pixbuf.postinst > > > > Could you comment on the above ? hmm, in principle that utility should be called, to make gdk-pixbuf aware of the jpeg-xl loader. Maybe a workaround would be to have $ cat libjxl-gdk-pixbuf.postinst #!/bin/sh -e for X in /usr/lib/*/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders do if [ -x ${X} ]; then ${X} --update-cache fi done #DEBHELPER# instead? And for libjxl-gdk-pixbuf.postrm this should also work. Or is there a better way, to get the library triplet for the architecture of the packet, that is being installed? Cheers, Julian > > Thanks -- () ascii ribbon campaign - against html e-mail /\ - against proprietary attachments
