[Pkg-sysvinit-devel] Bug#676520: [sysv-rc] System unsuitable for dep-based boot cannot configure

[Roger Leigh]

On Thu, Jun 07, 2012 at 05:34:33PM +0300, David Baron wrote:
> I have an older init scripted system which will not configure for dep-based 
> boot due to man missing lsb tags and overrides (what can I do about this?).

>From 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 <rleigh at debian.org>  Wed, 18 Apr 2012 23:30:37 +0100

> Additonally, as per bug #676463, there are numerous complaints about init 
> scripts for removed applications and some that are not removed!

These are, as said above, obsolete init scripts from removed (but
not purged) conffiles.  They lack LSB headers, and the packages
need purging to remove them.

> In the past, sysv-rc would configure for the old boot correctly and upgrades 
> went merrily on their way. Now, it gives an error return.
> 
> Sysv-rc is left unconfigured and NO other apt operations are possible!

This is intentional.  Previously, you had the option to either enable
dynamic dependency-based ordering, or stick with static legacy
ordering.  We now require dependency-based ordering, and static is
no longer supported.  So we can't continue until you've fixed the
system by removing the broken scripts.  We haven't really changed the
logic of the scripts here--we've just removed the choice of retaining
the legacy ordering.

For the next upload, I need to see if we can just enable it
unconditionally, irrespective of whether the broken scripts are
present or not.  If you can possibly mail me a copy of all the
broken scripts it identified, I'll test that possibility.  It will
make the transition much smoother.

Note that this only affects upgrades from older releases which lacked
LSB init scripts.  The reason for doing this is because the static
ordering is bitrotting, and is no longer being actively tested since
we are all now using dynamic ordering.  Rather than have systems start
to break as the ordering becomes progressively wrong, this will ensure
all systems will use a single correct ordering.


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