Re,
I've replied to #850948 where I think you wan't to discuss the piuparts-needrestart-* issue. 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]? So this is *no* policy violation since: - invoke-rc.d *should* be used - but it is not required - runing /etc/init.d/ initscripts *should* called by initscript subsystem - but it is not required - needrestart is *no* maintainer script at all, so 9.3.3 even does not apply, doesn't it [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3 I think the severity of this bug should be lowered to important since there is no policy violation of needrestart at all. 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). So you might consider to move the bug to init-system-helpers. 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. >> - the debconf pipe gets weirrd (consolation) > > I suspect this to be irrelevant in scenarios involving policy-rc.d. ACK >> - needrestart and debconf thinks you call them interactive... but they >> are called non-interactive. As a result they wait forever for >> interaction. > > Agreed. > > From my brief conversations with the piuparts developers I am of the > impression that piuparts a) makes use of policy-rc.d and b) tells > debconf that interaction is non-interactive, c) has a quite big track > record to support a) and b), d) have rarely if ever tested needrestart > being pulled in as a dependency due to very few packages depending on it > at all. 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. >> 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. HTH, Thomas > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private -- :: WWW: https://fiasko-nw.net/~thomas/ :: ::: Jabber: xmpp:tho...@jabber.fiasko-nw.net ::: :: flickr: https://www.flickr.com/photos/laugufe/ ::
