Package: dpkg Version: 1.20.9 X-Debbugs-Cc: jo...@debian.org Hi Guillem,
this issue is co-reported by josch. While working on DPKG_ROOT reproducibility, we observed that the trigger database differs for the foreign and native case. In the foreign case, packages would carry an architecture qualifier while a native case would lack them. The problem is actually entirely independent of DPKG_ROOT and can be reproduced in an essential chroot with e.g. amd64 native and i386 foreign. A simple example package is man-db. Installing man-db:amd64, gives a trigger database without architecture qualifiers while installing man-db:i386 gives one that includes them. This is a problem both to using DPKG_ROOT for creating foreign installations and for cross grading an installation. While this may be solved by improving dpkg's notion of which architecture is native when operating on a --root, I think in this case, always including the architecture qualifier (for architecture-dependent packages) would be the better option. You hinted that commit d658a8ec1110c9b3b20987cd903a54f59801117f may be at fault. I'm recording that here for your convenience. Helmut
