Package: ifupdown
Version: 0.6.7-0.1
Tags: patch

I discovered this issue when testing a dependency based boot system
based on insserv.  When replacing update-rc.d with a version tracking
dependencies, it require all scripts to be installed in dependency
order.  This is a problem for packages with several init.d scripts,
where dh_installinit will insert the scripts in the order it is called
and not in dependency order.  I found this in the ifupdown postinst:

  # Automatically added by dh_installinit
  if [ -x "/etc/init.d/ifupdown" ]; then
          update-rc.d ifupdown start 39 S . start 36 0 6 . >/dev/null || exit $?
  fi
  # End automatically added section
  # Automatically added by dh_installinit
  if [ -x "/etc/init.d/ifupdown-clean" ]; then
          update-rc.d ifupdown-clean start 18 S . >/dev/null || exit $?
  fi
  # End automatically added section

The problem here is that ifupdown depend on ifupdown-clean (according
to the override files in insserv, the scripts themselves are yet to be
updated, see bug #330230), and insserv refuses to insert ifupdown
before ifupdown-clean is inserted.  update-rc.d return an error and
the postinst terminates before ifupdown-clean is inserted.

A solution for this problem is to reorder the two calls to
dh_installinit in debian/rules, to install ifupdown-clean first:

--- ifupdown-0.6.7/debian/rules.orig    2006-09-10 12:20:02.000000000 +0200
+++ ifupdown-0.6.7/debian/rules 2006-09-10 12:20:16.000000000 +0200
@@ -142,8 +142,8 @@
        dh_installmenu
 #      dh_installemacsen
 #      dh_installpam
-       dh_installinit --name=ifupdown --no-start -- start 39 S .  start 36 0 6 
.
        dh_installinit --name=ifupdown-clean --no-start -- start 18 S .
+       dh_installinit --name=ifupdown --no-start -- start 39 S .  start 36 0 6 
.
        dh_installcron
 #      dh_installmanpages
 #         ^-- can't do our symlink trick

With this change, the postinst work fine with an dependency based boot
system.

Friendly,
-- 
Petter Reinholtdsen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to