Package: libglib2.0-dev Version: 2.42.1-1 Dear Maintainer,
I try the Riku's patch above (glib-ma-fixed.patch). Disclaimer, I rebase the patch myself so maybe I break it. Anyway, I manage to broke dpkg install. Here some information that I hope would be useful and avoid the same failure as me. Dpkg error: --------------------------------------------------------------------------------- (Reading database ... 237158 files and directories currently installed.) Removing libglib2.0-dev:i386 (2.42.1-2) ... dpkg-query: error: --listfiles needs a valid package name but 'libglib2.0-dev' is not: ambiguous package name 'libglib2.0-dev' with more than one installed instance Use --help for help about querying packages. Traceback (most recent call last): File "/usr/bin/pyclean", line 117, in <module> main() File "/usr/bin/pyclean", line 101, in main pfiles = set(dpf.filter_out_ext(pfiles, ('.so',))) File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext for fn in files: File "/usr/share/python/debpython/namespace.py", line 77, in add_namespace_files for fn in files: File "/usr/share/python/debpython/files.py", line 53, in from_package raise Exception("cannot get content of %s" % package_name) Exception: cannot get content of libglib2.0-dev dpkg: error processing package libglib2.0-dev:i386 (--purge): ----------------------------------------------------------------------------------- I try to debug it. I think it is related to the content of prerm script. As you can see it uses a dpkg call without the architecture information (:amd64) ----------------------------------------------------------------------------------- cat /var/lib/dpkg/info/libglib2.0-dev:amd64.prerm #!/bin/sh set -e # Automatically added by dh_python2: if which pyclean >/dev/null 2>&1; then pyclean -p libglib2.0-dev else dpkg -L libglib2.0-dev | grep \.py$ | while read file do rm -f "${file}"[co] >/dev/null done fi # End automatically added section ----------------------------------------------------------------------------------- Based on the comment I think it is related to those 2 lines in the rule file. binary-install/libglib2.0-dev:: dh_python2 -plibglib2.0-dev /usr/share/glib-2.0/codegen I'm gussing it must be somewhat contain :arch (maybe $(DEV_PKG)). As a side note, it would be very nice to have a multiarch glib-dev package for the next release. Best regards, Gregory