Hello Andreas, Andreas Henriksson [2016-11-09 11:08 +0100]: > As discussed on IRC we seem to agree that an init-less chroot which does > not have a policy-rc.d blocking service actions isn't a sane > configuration. This patch auto-detects the situation and skips running > the invoke-rc.d action (aka policy-rc.d code 101), unless --force was > given. In both situations a warning message is (also) printed.
I must absolutely and loudly protest against mass-killing birds! ☺ However, I do like the patch, it would give us a much saner behaviour of package installation in self-created chroots. mk-sbuild and friends do install a policy-rc.d already, but I've seen this come up more than once already. In the past where SysV and /etc/init.d/ were "the thing" it could still be argued that one doesn't need an explicit "init system" for some situations, but with Debian supporting multiple ones (and systemd by default) this is entirely moot IMHO. Michael, any others: Do you see any downside of this? Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
