Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: britney X-Debbugs-Cc: gobject-introspect...@packages.debian.org, debian-cr...@lists.debian.org
gobject-introspection in experimental has this in https://release.debian.org/britney/pseudo-excuses-experimental.html#gobject-introspection: gobject-introspection (1.78.1-6 to 1.78.1-9) Migration status for gobject-introspection (1.78.1-6 to 1.78.1-9): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: gobject-introspection/amd64 has unsatisfiable dependency gobject-introspection/arm64 has unsatisfiable dependency Additional info: uninstallable on arch amd64, not running autopkgtest there uninstallable on arch arm64, not running autopkgtest there The gobject-introspection binary package *is* installable, and in fact I have it installed locally. Taking the amd64 version as an example, it depends on: - binutils-x86-64-linux-gnu:any, a real Multi-Arch: allowed package - gcc-x86-64-linux-gnu, a virtual package provided by gcc:amd64 - gobject-introspection-bin | qemu-user | qemu-user-static, where g-i-bin is a Multi-Arch: allowed package from the same source - gobject-introspection-little-endian:any, a virtual package provided by g-i-bin, which is Multi-Arch: allowed (experimentally, apt and dpkg both seem to be happy to assume that this makes the gobject-introspection-little-endian virtual package behave as though it was also Multi-Arch: allowed) - pkgconf, a real package - python3:any, a real Multi-Arch: allowed package I think all of those are correct? Or do I need to make gobject-introspection-bin Multi-Arch: foreign, drop the :any from gobject-introspection-little-endian:any, and replace the gobject-introspection-bin | qemu-user | qemu-user-static dependency by python3 | qemu-user | qemu-user-static or similar? My goal here is that you can install gobject-introspection:amd64 on an amd64 machine, or on any other little-endian machine that will be able to cross-compile amd64 binaries and then run them by explicitly invoking them via qemu-user, as discussed with Helmut Grohne at the recent Cambridge miniDebconf. (It has to be little-endian because g-ir-inspect and similar tools don't currently support byte-swapping fields in binary typelibs.) Thanks, smcv
