[Pkg-sysvinit-devel] Bug#738775: insserv: Insserv 1.16 tries to connect to systemd even though system is running on sysv-init

[Jan Binder]

Am Mittwoch, 12. Februar 2014, 22:04:20 schrieben Sie:
> Control: reassign 738532 insserv
> Control: found 738532 1.16.0-1
> 
> [Jan Binder]
> 
> > Dear Maintainer,
> 
> Thank you for your report.  Very glad to have more testers of the new
> insserv version. :)
> 
> >    * What led up to the situation?
> >    
> >     After having installed insserv 1.16, installing any version of
> >     initscripts
> >     leads to the error message shown in bug #738532.
> 
> How strange.  This do not happen when I test.  Do you have the
> /run/systemd/private file?  I do not.
No, that particular file is not there. The parent directory, however, exists 
and has some more directories in it.

> <URL: https://bugs.debian.org/738532 > should definitely be reassigned
> to sysv-rc or insserv, and insserv seem like the most likely cause
> given the messages. :)
Yeah, I saw that when searching for the error message.

> >    * What was the outcome of this action?
> >    Cannot install initscripts after installing insserv 1.16 because
> >    it tries to connect to systemd which is present on the system but
> >    not used as PID 1.
> 
> I do not have systemd installed.  Perhaps installing it is enough to
> confuse insserv to expect it to be running?
That might be enough.

> >    * What outcome did you expect instead?
> >    insserv should not fail when it cannot connect to systemd and
> >    systemd is not running as PID 1.  Instead it should talk to
> >    sysv-init or whatever else it supports.
> 
> I agree.
> 
> I am not sure if grave is the correct severity, given that insserv
> seem to work for machines without systemd installed, but keeping it
> currently as this bug is some kind of RC and definitely should not
> make it into testing even if someone by mistake upload 1.16 into
> unstable.

There are now more than ten packages in experimental/unstable that depend on 
systemd, including most of gnome, network-manager and pcscd (this pulls 
systemd for me), so that is a sensible precaution.

Greetings,
Jan Binder