On 12.02.2012 13:48, Neil Williams wrote: > Package: libglib2.0-0 > Version: 2.30.2-6 > Severity: normal > > With the new upload of zlib1g, it is now possible to install glib > as a Multi-Arch package. It works for i386 on amd64 but not for > armel on amd64 - due to execution of the wrong executable > in the maintainer scripts: > > Setting up libglib2.0-0:armel (2.30.2-6) ... > /usr/lib/arm-linux-gnueabi/glib-2.0/glib-compile-schemas: 1: > /usr/lib/arm-linux-gnueabi/glib-2.0/glib-compile-schemas: Syntax error: word > unexpected (expecting ")") > /usr/lib/arm-linux-gnueabi/glib-2.0/gio-querymodules: 1: > /usr/lib/arm-linux-gnueabi/glib-2.0/gio-querymodules: Syntax error: word > unexpected (expecting ")") > dpkg: error processing libglib2.0-0:armel (--configure):
Those tools are dpkg triggered. Afaics, we will have this issue in various packages: libgdk-pixbuf2.0-0 libgtk2.0-0 libgtk-3-0 libglib2.0-0 They all install path based triggers which call a support binary from the multi-arch library path. In all cases, aside gio-querymodules, there is an added || true. I assume we should just do the same for gio-querymodules. This way, we'd still get the error messages, but the packages would install properly. Unless someone has a nicer idea how to handle dpkg triggers in the new multi-arch world. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
