Bug#754404: /usr/sbin/invoke-rc.d: line 288: /sbin/runlevel: No such file or directory

[Michael Biebl]

reassign 754404 systemd-sysv
thanks

Am 10.07.2014 22:32, schrieb 積丹尼 Dan Jacobson:
>>>>>> "MB" == Michael Biebl <biebl at debian.org> writes:
> 
> MB> Please provide a complete apt log.
> 
> Start-Date: 2014-07-11  01:47:04
> Install: systemd-sysv:i386 (208-5)
> Upgrade: libsystemd-daemon0:i386 (208-3, 208-5), systemd:i386 (208-3, 208-5), libsystemd-login0:i386 (208-3, 208-5), libpam-systemd:i386 (208-3, 208-5), libsystemd-journal0:i386 (208-3, 208-5)
> Remove: sysvinit-core:i386 (2.88dsf-55.2)
> End-Date: 2014-07-11  01:47:31
> 
> Log started: 2014-07-11  01:47:04
> Preparing to unpack .../libsystemd-journal0_208-5_i386.deb ...
> Unpacking libsystemd-journal0:i386 (208-5) over (208-3) ...
> Setting up libsystemd-journal0:i386 (208-5) ...
> Processing triggers for libc-bin (2.19-5) ...
> Preparing to unpack .../libsystemd-login0_208-5_i386.deb ...
> Unpacking libsystemd-login0:i386 (208-5) over (208-3) ...
> Setting up libsystemd-login0:i386 (208-5) ...
> Processing triggers for libc-bin (2.19-5) ...
> dpkg: sysvinit-core: dependency problems, but removing anyway as you requested:
>  sysvinit depends on sysvinit-core | upstart | systemd-sysv; however:
>   Package sysvinit-core is to be removed.
>   Package upstart is not installed.
>   Package systemd-sysv is not installed.
> 
> Removing sysvinit-core (2.88dsf-55.2) ...
> Processing triggers for man-db (2.6.7.1-1) ...
> Preparing to unpack .../libsystemd-daemon0_208-5_i386.deb ...
> Unpacking libsystemd-daemon0:i386 (208-5) over (208-3) ...
> Setting up libsystemd-daemon0:i386 (208-5) ...
> Processing triggers for libc-bin (2.19-5) ...
> Preparing to unpack .../systemd_208-5_i386.deb ...
> Unpacking systemd (208-5) over (208-3) ...
> Processing triggers for dbus (1.8.6-1) ...
> /usr/sbin/invoke-rc.d: line 288: /sbin/runlevel: No such file or directory
> [....] system message bus already started; not starting.?25l1G[32m ok 39;49m?12l?25h.
> Processing triggers for man-db (2.6.7.1-1) ...
> Setting up systemd (208-5) ...
> Selecting previously unselected package systemd-sysv.
> Preparing to unpack .../systemd-sysv_208-5_i386.deb ...
> Unpacking systemd-sysv (208-5) ...
> Processing triggers for man-db (2.6.7.1-1) ...
> Setting up systemd-sysv (208-5) ...
> Preparing to unpack .../libpam-systemd_208-5_i386.deb ...
> Unpacking libpam-systemd:i386 (208-5) over (208-3) ...
> Processing triggers for man-db (2.6.7.1-1) ...
> Setting up libpam-systemd:i386 (208-5) ...
> Log ended: 2014-07-11  01:47:31

Which version of the sysvinit package is installed?

The /sbin/runlevel utility is shipped by both sysvinit-core and
systemd-sysv. That's why they Conflict/Replace  each other.

Apparently apt removed sysvinit-core and the trigger was processed
before systemd-sysv was installed.

sysvinit is Essential and Pre-Depends on sysvinit-core | systemd-sysv.

I'm a bit at a loss here how we can avoid the dbus trigger to be
processed while systemd-sysv is not yet unpacked.


We could drop the Conflicts: sysvinit-core from systemd-sysv and only
keep the Replaces, but that has it's downsides as well. So I'd like to
avoid that.


Maybe the dbus or dpkg maintainers have an idea.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140710/42053d57/attachment-0002.sig>