/etc/init.d/networking has ifupdown in Required-Start

[Nick Wellnhofer]

Binary package hint: netbase

This is only a problem if you use insserv to manage your init scripts. /etc/init.d/bootlogs.sh has ifupdown in Required-Start, but the ifupdown init script seems to have been removed. So insserv complains about that and the package can't be configured.

[Martin-Éric Racine (q-funk)]

What happens is this:

(Reading database ... 168470 files and directories currently installed.)
Preparing to replace ifupdown 0.6.8ubuntu19 (using .../ifupdown_0.6.8ubuntu19_i386.deb) ...
Unpacking replacement ifupdown ...
Preparing to replace netbase 4.35ubuntu1 (using .../netbase_4.35ubuntu1_all.deb) ...
Unpacking replacement netbase ...
Setting up netbase (4.35ubuntu1) ...
insserv: Service ifupdown has to be enabled to start service networking
insserv: exiting now!
dpkg: error processing netbase (--install):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of ifupdown:
 ifupdown depends on netbase (>= 4.30ubuntu2); however:
  Package netbase is not configured yet.
dpkg: error processing ifupdown (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db ...
Errors were encountered while processing:
 netbase
 ifupdown

*****
In addition, there's a dependency cycle, in that the ifupdown package Depends: netbase, however netbase init Requires-Start: ifupdown. The only way to solve it is to disable insserv, but that is only a lame workaround. Fixing these two packages' interrelationships is what's needed.

[Nick Wellnhofer (nick-aevum)]

This is fixed in Karmic.

[Stéphane Graber (stgraber)]

Ubuntu doesn't use insserv so this bug should never have happened to start with. As Nick stated, this bug has been fixed since Karmic and won't be relevant with 12.10 where that init script is replaced by an upstart job.