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

Dmitry Bogatov KAction at debian.org
Sun Jan 13 13:31:36 GMT 2019


[2019-01-11 14:51] Felipe Sateler <fsateler at debian.org>
> On Fri, Jan 11, 2019 at 9:39 AM Dmitry Bogatov <KAction at debian.org> wrote:
> 
> >
> > [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.
> >
> 
> They are already mapped to `defaults`.

I know. Would you be interested in patch, that removes these aliases at
all? And what about removing sysv_plain?

> > What worries me is that `update-rc.d defaults' do not seems to
> > work (insserv=1.18.0):
> > [...]
> To preserve admin modifications, `update-rc.d defaults` must not touch any
> existing links. That's documented in the manpage:
> 
> If  any files named /etc/rcrunlevel.d/[SK]??name already exist then
> update-rc.d does nothing.

Thank you for explanation. I believe this bug should be closed, but
leaving it to owner's maintainer.



More information about the Pkg-systemd-maintainers mailing list