severity 676463 serious severity 676520 serious forcemerge 676463 676520 thanks
On Thu, Jun 07, 2012 at 09:09:55AM +0200, Paul Menzel wrote: > in contrast to earlier versions, with this version installation of > `sysv-rc` fails when migration to dependency based boot fails. > Additionally it complains about obsolete init.d scripts of packages > which were never a problem before and whose init.d scripts do not seem > to be obsolete. Previously, sysv-rc gave you two options: legacy bootordering or dependency based bootordering. You could keep the broken scripts and remain with legacy, or you could clean up the scripts and enable dependency bootordering. The change here is that we now require you to migrate to dependency based bootordering, because we will no longer support legacy static ordering. Please have a read through the details in NEWS.Debian: +sysv-rc (2.88dsf-23) experimental; urgency=low + + Dependency based boot ordering is now required. + + Most systems will already be using dependency based boot ordering. + This includes all squeeze and later releases, unless you have taken + deliberate action to disable it. Installations upgraded from etch, + lenny or earlier releases will have enabled dependency based booting + when upgrading to squeeze and later releases. However, it was + previously possible to opt out of migrating to dependency based + booting and retain static boot ordering. This is no longer the case. + + If your system is still using static boot ordering, migrating to + dependency based boot ordering will be performed when sysv-rc is + configured. If this is not possible for any reason, you will have to + correct the problem before upgrading can continue. It will not be + possible to complete the upgrade until insserv is configured. + + The most commonly encountered problem preventing migration is the + presence of obsolete init scripts from removed (but unpurged) + packages. If this is the case, you will be prompted with + instructions detailing how to purge these old packages. + + If you have custom init scripts, please ensure that these have the + correct dependency information in an LSB header so that they will be + run at the correct point in the boot sequence. + + -- Roger Leigh <rle...@debian.org> Wed, 18 Apr 2012 23:30:37 +0100 > sysv-rc (2.88dsf-26) wird eingerichtet ... > info: Checking if it is safe to convert to dependency based boot. > > error: Unable to migrate to dependency based boot sequencing. > error: Problems detected: package fuse left obsolete init.d script > behind, package initscripts left obsolete init.d script behind, package > initscripts left obsolete init.d script behind, package initscripts left > obsolete init.d script behind, package libchipcard-tools left obsolete init.d > script behind, package smartmontools left obsolete init.d script behind, , > package gdm removed but not purged > > If this is due to the presence of unpurged obsolete initscripts, > it is suggested that the following is run to remove them: > dpkg --purge fuse initscripts initscripts initscripts > libchipcard-tools smartmontools This is wrong; we shouldn't be purging initscripts. Could you possibly let me know which specific files were left behind which were causing problems? We should be able to correct this during the upgrade. > Also the other init.d scripts are packaged properly. Yes. The ones causing problems aren't current ones, they are obsolete ones left by removed (but not purged) packages. Purging the packages will remove them, allowing you to continue. Ideally, we could do this automatically. I intend to look into whether we can just enable it even though the old scripts are still present. If it's safe, it will make this much less painful. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org