Quoting Thomas Liske (2017-01-14 16:09:26) > I've replied to #850948 where I think you wan't to discuss the > piuparts-needrestart-* issue.
Thanks for correcting my error (I realized it only after posting) > Jonas Smedegaard <d...@jones.dk> writes: > >> Maybe it is just a debconf frontend issue? In cases needrestart > >> does seems to hang it trackes down to: > >> > >> - daemons hangig while restarting them (init scripts) > > > > Agreed. This would imply that either piuparts fail to setup > > policy-rc.d appropriately, or that needrestart ignores policy-rc.d. > > The latter is a Policy violation. > > You are referencing Debian Policy's section 9.3.3 [1]? Correct. Sorry for sloppily not mentioning it explicitly. [...] > 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 uses the service command of init-system-helpers to restart > daemons. A quick look into /usr/sbin/service shows that if there is no > systemd the service command calls the init script directly (look at > run_via_sysvinit). Thanks for clarifying. > So you might consider to move the bug to init-system-helpers. No need: init-system-helpers provide tools both to interacti via policy-rc.d and tools to bypass that layer - which is perfectly fine. Problem is when package install routines (even if indirectly - e.g. using inappropriate helper tools) bypass policy-rc.d. > 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. Please do. That sounds like it would solve this issue. [...] > Needrestart's use of debconf should be aware if piuparts already tells > debconf that it is called non-interactive. So it seems to hang due to > some init scripts problem as discussed above. Agreed. >>> Feel free to open a new bug to needrestart to track down this issue. >> >> Thanks for the suggestion. I am not familiar with piupart I will >> likely not do so, but welcome others to pick up where I left. > > Neighter do I. Another workaround could be to change needrestart to > list only mode within piupart using some local config snippet as they > do for policy-rc.d. If I understand you corretly, that you suggest to invent a mechanism essentially doing the same as policy-rc.d, then I see no need for that: Please respect the already existing policy-rc.d instead. I guess what you seek is a solution not specific to Debian - and find that wuite sensible. I suspect, however, that there is no XDG or similar more generic standard for respecting deployment-specific hooks - which is really what policy-rc.d is about (not only chroot support). Regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
