Bug#573550: affects squeeze, package has only been updated in testing

Dmitry Bogatov KAction at debian.org
Fri Jan 11 12:37:01 GMT 2019


[2019-01-01 22:38] Dmitry Bogatov <KAction at debian.org>
> [2018-12-29 19:51] Michael Biebl <biebl at debian.org>
> > Am 29.12.18 um 19:34 schrieb Dmitry Bogatov:
> > > control: reassign -1 init-system-helpers
> > 
> > How should we handle bugs that are really sysvinit specific, even if
> > they affect update-rc.d/invoke-rc.d (i.e. init-system-helpers)
> > 
> > No one of the current init-system-helpers is using sysvinit anymore, so
> > bug reports like this one are bound to get forgotten/ignored.
> 
> Quite unfortunate situation. Okay, I will take a look at it myself.
> 
> > Should we usertag them somehow so those sysvinit specific issues are
> > on the radar on the sysvinit maintainers?  This really needs a
> > fix/patch from someone actively using sysvinit.
>
> Just added usertag.

Okay. I believe this bug could be closed on timeout, and both 'start'
and 'stop' sub-actions could be dropped, together with `sysv_plain'
(pre-boot-dependency) part.

What worries me is that `update-rc.d defaults' do not seems to
work (insserv=1.18.0):

  # update-rc.d cron disable 3
  insserv: warning: current start runlevel(s) (2 4 5) of script `cron' overrides LSB defaults (2 3 4 5).
  insserv: warning: current stop runlevel(s) (3) of script `cron' overrides LSB defaults (empty).
  # update-rc.d cron defaults
  insserv: warning: current start runlevel(s) (2 4 5) of script `cron' overrides LSB defaults (2 3 4 5).
  insserv: warning: current stop runlevel(s) (3) of script `cron' overrides LSB defaults (empty).
  # insserv cron
  insserv: warning: current start runlevel(s) (2 4 5) of script `cron' overrides LSB defaults (2 3 4 5).
  insserv: warning: current stop runlevel(s) (3) of script `cron' overrides LSB defaults (empty).
  # insserv cron -f
  insserv: warning: current start runlevel(s) (2 4 5) of script `cron' overrides LSB defaults (2 3 4 5).
  insserv: warning: current stop runlevel(s) (3) of script `cron' overrides LSB defaults (empty).
  # update-rc.d cron enable 3

As can be seen, neither `update-rc.d defaults' nor direct invocation of
/sbin/insserv do not restore runlevels, prescribed by LSB header. Jesse,
am I doing it wrong?



More information about the Pkg-systemd-maintainers mailing list