What has changed in the actions of dpkg --unpack recently which has altered the detection of which packages remain to be configured? A chroot created with multistrap now fails to configure because dpkg --configure -a not only does not identify any packages as needing configuration but also changes the status from install ok unpacked to install ok installed for every package without doing any work. (dpkg --unpack cannot be used directly because multistrap is not operating natively and cannot execute anything within the chroot.) I can't see any differences currently in the files in /chroot/var/lib/dpkg/ between using dpkg --unpack (native architecture) and the multistrap method (native or foreign). Can we look again at a way of unpacking a .deb which is architecture-neutral but still allows the package to be configured once the fs is accessed under the appropriate arch? -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgpGrjyUjc5wz.pgp
Description: PGP signature