Dear init-system-helpers maintainers, 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/12
the Release Team announced the freeze dates for bookworm, so I wanted to send another friendly ping about this bug and the MR above. I think the longer this change is tested the more chances I have to fix any bugs that my patch might've introduced before the bookworm release. If you don't have time to prepare the upload, I can also take care of that and do a team upload just as Luca recently did. What do you think? Thanks! cheers, josch
signature.asc
Description: signature
