[Pkg-sysvinit-devel] Bug#789008: dbus: Unable to configure package (dpkg)

[Simon McVittie]

Control: reassign 789008 insserv
Control: forcemerge 746170 789008

On 17/06/15 05:45, Ludovic Lebègue wrote:
> dbus cannot be configured during install from 'experimental'.

Everything that installs an init script is going to have the same
problem on your system. This is not dbus breaking sane and exim4; it is
some combination of rpcbind, nfs-common and insserv breaking all of
dbus, sane and exim4.

I can't tell for sure because your bug report doesn't have version
numbers for insserv, nfs-common or rpcbind, but it seems to be the same
thing as <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746170> so
I'm merging it.

> -- System Information:
> Debian Release: stretch/sid
>   APT prefers experimental
>   APT policy: (1, 'experimental')

You seem to be using experimental as if it was a complete and
self-contained suite. It isn't. Users of experimental are expected to
keep the apt sources for unstable, *add* experimental, and pick
*individual* bleeding-edge packages from experimental for installation.
Using packages from experimental without a specific reason is generally
a bad idea.

insserv appears to have a version in experimental from over a year ago,
which never made it into unstable, and has a release-critical bug from
back then, #746170.

I suggest fixing your apt sources, and switching insserv, rpcbind and
nfs-common (and everything else you aren't specifically interested in
for that matter) to their versions from unstable; get a working system
before you start breaking it with experimental.

If you are going to be using anything from unstable or experimental, I
strongly recommend apt-listbugs - it would have told you about #746170
before you even installed the experimental insserv.

> Setting up dbus (1.9.16-2) ...
> A reboot is required to replace the running dbus-daemon.
> Please reboot the system when convenient.

This part is expected, correct and harmless.

> insserv: FATAL: service rpcbind is missed in the runlevels 2 3 4 5 to use
> service nfs-common
> insserv: exiting now!
> update-rc.d: error: insserv rejected the script header
> dpkg: error processing package dbus (--configure):
>  subprocess installed post-installation script returned error exit status 1

This part is bad. insserv reports that rpcbind and nfs-common are
inconsistent, and as a result, refuses to run "update-rc.d dbus
defaults" to enable dbus...

> Setting up exim4-base (4.86~RC1-3) ...
> insserv: FATAL: service rpcbind is missed in the runlevels 2 3 4 5 to use
> service nfs-common
> insserv: exiting now!
> update-rc.d: error: insserv rejected the script header

... and also refuses to run "update-rc.d exim4 ..." to enable exim4 ...

> Setting up sane-utils (1.0.25+git20150528-1) ...
> insserv: FATAL: service rpcbind is missed in the runlevels 2 3 4 5 to use
> service nfs-common
> insserv: exiting now!
> update-rc.d: error: insserv rejected the script header

... and also refuses to run "update-rc.d saned ..." to enable sane.

This is a bug in insserv, rpcbind and/or nfs-common. I don't know which
of the three packages is actually at fault here, and there seems to have
been some dispute about that question, but the bug report I'm merging it
into is currently assigned to insserv.

Regards,
    S