Hallo Dresden,

Ich habe eben testweise eine Debian-stable Kiste auf testing migriert. Beim Einführen des dependency-based boot system kam mir folgende Meldung entgegen:

<snip> Unable to migrate to dependency-based boot system

Tests have determined that problems in the boot system exist which prevent migration to dependency-based boot sequencing:

insserv: There is a loop between service rmnologin and mountnfs if started, insserv: loop involving service mountnfs at depth 7, insserv: loop involving service portmap at depth 6, insserv: There is a loop between service rmnologin and mountall if started, insserv: loop involving service mountall at depth 4, insserv: loop involving service checkfs at depth 3, insserv: loop involving service mountnfs-bootclean at depth 10, insserv: There is a loop between service rmnologin and mountoverflowtmp if started, insserv: loop involving service mountoverflowtmp at depth 6, insserv: loop involving service mountall-bootclean at depth 5, insserv: There is a loop between service rmnologin and mountdevsubfs if started, insserv: loop involving service mountdevsubfs at depth 2, insserv: loop involving service udev at depth 1, insserv: There is a loop between service rmnologin and ifupdown-clean if started, insserv: loop involving service ifupdown-clean at depth 3, insserv: loop involving service checkroot at depth 2, insserv: loop involving service networking at depth 8, insserv: loop involving service lvm2 at depth 4,

If the reported problem is a local modification, it needs to be fixed manually. If it's a bug in the package, it should be reported to the BTS and fixed in the package. See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for more information about how to fix the problems preventing migration.

To reattempt the migration process after the problems have been fixed, run "dpkg-reconfigure sysv-rc". <snap>

Da ich mir keiner lokalen Änderungen bewußt bin, habe ich nach dem fertigen "cupt full-upgrade" einfach "dpkg-reconfigure sysv-rc" eingetippt, welches auch sauber durchlief (logfile hängt an).

Ich gehe davon aus, daß es sich um einen temporären Fehler handelte, weil zu dem Zeitpunkt evntl. noch einige init-Skripte keinen passenden Header hatten. Eine Reboot funktionierte auch, damit sehe ich keinen Handlungsbedarf. Gegenmeinungen? Wenn ja, wie finde ich das Paket zum Bug-Einkippen?

Danke, Hilmar