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

Petter Reinholdtsen pere at hungry.com
Thu Feb 13 10:11:26 UTC 2014

I've tried to reproduce this part of your problem report:

> * 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 have no problem installing initscripts or any other package, even if
insserv spew out lots of error messages.  So the problem you reported
seem to be non-fatal and irrelevant for any installation problem.  Can
you tell me more about how the installation of initscripts fail?

The svn version of insserv reduces the amount of messages, but are
still printing warnings.  The behaviour do not change, as far as I can

Happy hacking
Petter Reinholdtsen

More information about the Pkg-sysvinit-devel mailing list