Am 24.09.2021 um 08:15 schrieb Johannes Schauer Marin Rodrigues:
Hi Martin, Felipe & Michael,Quoting Johannes Schauer Marin Rodrigues (2021-08-20 21:33:00)Quoting Johannes 'josch' Schauer (2021-02-24 00:14:16)if dpkg (since 1.18.5) is run with --force-script-chrootless, it sets the variable DPKG_ROOT to the directory into which dpkg will install the requested packages. This is useful for bootstrapping, creating chroots for foreign architectures where utilities from inside the chroot cannot be executed, avoiding dependency loops between postinst scripts, installation without requiring superuser privileges and for creating installations that do not even contain dpkg. See https://wiki.debian.org/Teams/Dpkg/Spec/InstallBootstrap for more information. Currently, when maintainer scripts are run, /usr/sbin/policy-rc.d is checked to avoid starting services. But instead, the scripts should check "$DPKG_ROOT/usr/sbin/policy-rc.d". In normal situations, the $DPKG_ROOT variable is empty, so this will work as usual. But if dpkg is run with --root and --force-script-chrootless then /usr/sbin/policy-rc.d from the new root directory will be used.for your convenience, I have created a merge request on salsa which implements the changes that make DPKG_ROOT work in our testing environment. https://salsa.debian.org/debian/init-system-helpers/-/merge_requests/12would you mind me applying the above merge request and doing an NMU of init-system-helpers?
Didn't have time yet to look at this. Sorry.From a cursory glance it feels inelegant having to sprinkle env vars across everything. This also feels like it could get easily broken when changes are made. So I'm not too enthusiastic tbh.
OpenPGP_signature
Description: OpenPGP digital signature
