On Sat, 14 Jan 2017 23:56:24 +0100 Thomas Liske <tho...@fiasko-nw.net> wrote: > Jonas Smedegaard <d...@jones.dk> writes: > > >> I think the severity of this bug should be lowered to important since > >> there is no policy violation of needrestart at all. > > > > I think it is quite worrisome if simply installing (not actively using) > > needrestart inside a chroot spawns daemons - and that is not treated as > > serious (no matter framed by some geleral Debian Policy wording). > > Needrestart was never written nor designed to run within a chroot. This > use case does not make any sense at all. Just don't do it (should be > added to the README ;-) .
Still packages must behave sanely if installed in a chroot (e.g. when being used as Build-Depends) - and most of them do. Just think about things like udev, grub, ... There is also an ischroot command in debianutils that could be helpful to detect that "unusual" condition from the maintainer scripts. > >> I (upstream) or Patrick (maintainer) could add a patch to needrestart > >> to use invoke-rc.d instead of the service command. That would only be > >> a Debian specific workaround. See https://bugs.debian.org/656081 for an old discussion that 'service' is for the local admin does not respect policy-rc.d by design and therefore is not suitable for use im maintainer scripts - neither directly nor transitively. Andreas
