[Pkg-sysvinit-devel] Bug#694252: sysv-rc: migration to dependency based boot order fails if bootchart from lenny is still installed
Andreas Beckmann
debian at abeckmann.de
Sat Nov 24 18:34:09 UTC 2012
Package: sysv-rc
Version: 2.88dsf-32
Severity: important
User: debian-qa at lists.debian.org
Usertags: piuparts
Control: affects -1 + bootchart
Hi,
during a test with piuparts I noticed an error while enabling the
dependency based boot sequencing if the bootchart package from lenny is
still installed.
>From the attached log:
Preparing to replace sysv-rc 2.88dsf-13.1+squeeze1 (using .../sysv-rc_2.88dsf-32_all.deb) ...
Unpacking replacement sysv-rc ...
Setting up sysv-rc (2.88dsf-32) ...
info: Reordering boot system, log to /var/lib/insserv/run-20121123T0359.log
error: Something failed while migrating.
error: Unable to migrate to dependency based boot sequencing.
See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for
more information about dependency based boot sequencing. To
reattempt the migration process run 'dpkg --configure sysv-rc'.
dpkg: error processing sysv-rc (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
sysv-rc
and /var/lib/insserv/run-20121123T0359.log contains:
info: Converting rc0.d/S* and rc6.d/S* to K*.
info: running insserv
insserv: There is a loop at service bootchart if started
insserv: There is a loop at service rmnologin if started
insserv: There is a loop between service rmnologin and mountall if started
insserv: loop involving service mountall at depth 1
insserv: There is a loop between service rmnologin and mountnfs if started
insserv: loop involving service mountnfs at depth 2
insserv: loop involving service mountoverflowtmp at depth 1
insserv: loop involving service urandom at depth 5
insserv: loop involving service checkfs at depth 3
insserv: loop involving service mountnfs-bootclean at depth 6
insserv: There is a loop between service rmnologin and mountoverflowtmp if started
insserv: loop involving service mountall-bootclean at depth 7
insserv: There is a loop between service rmnologin and bootlogd if started
insserv: loop involving service bootlogd at depth 2
insserv: loop involving service mountdevsubfs at depth 1
insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true!
...
insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: loop involving service bootlogs at depth 1
insserv: Starting bootchart depends on rmnologin and therefore on system facility `$all' which can not be true!
insserv: loop involving service hostname at depth 4
insserv: exiting now without changing boot order!
This was observed on a distupgrade test from lenny to squeeze to wheezy.
There is no bootchart package in squeeze, but since there were no conflicts
the lenny package has been kept installed in squeeze, too.
Wheezy comes with an updated bootchart package, but sysv-rc got upgraded first.
Maybe a Breaks/Conflicts could be inserted somewhere to
ensure that bootchart gets upgraded first.
cheers,
Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bootchart_0.10~svn407-3.3.log.gz
Type: application/x-gzip
Size: 30934 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20121124/58549101/attachment-0001.bin>
More information about the Pkg-sysvinit-devel
mailing list