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

[Petter Reinholdtsen]

[Jan Binder]
> Ok, I agree that the systemd messages are gone with the SVN version
> and were not fatal:

Good.  I'll upload a les noisy version to experimental.

> Setting up initscripts (2.88dsf-49) ...
> insserv: FATAL: service dnsmasq is missed in the runlevels 2 3 4 5 to use service cups-browsed
> insserv: FATAL: service rpcbind is missed in the runlevels 2 3 4 5 to use service nfs-common
> insserv: exiting now!

Hm, this seem to be a problem with the complete set of scripts on your
machine.  Can you send the output from /usr/share/insserv/make-testsuite
on the machine in question?  It should allow me to reproduce your
problem.

> So it looks like the real problem is that insserv has problems with
> some script headers, especially rpcbind (see also bug #738532) and
> dnsmasq.  I don't know if there is anything wrong with those
> initscripts, but insserv dies and update-rc.d does not like that and
> returns an error which in turn dpkg does not like.

Seem to me insserv got more picky about runlevel settings.  Will have to
investigate this a bit more to be sure, as I have not seen this myself
in my testing.

> I have attached the offensive initscripts, they are from dnsmasq
> 2.68-1 and rpcbind 0.2.1-2 despite not knowing what is wrong with them
> or any other part of my init configuration.

Thanks.  The output from make-testsuite is better to try to reproduce
the problem.

-- 
Happy hacking
Petter Reinholdtsen