Package: netbase
Version: 4.37
Severity: important

When building a system from 'bare metal', it is possible to have initscripts
unpacked but not configured. As insserv is the default for new installs, the
configuration of netbase then tries to setup networking only to find that
mountkernfs is not enabled because initscripts is not configured.

If a package requires that another package must be configured before it can
be configured itself, a normal Depends: would be necessary. (Policy 7.2).

Setting up insserv (1.12.0-14em1) ...
...
Setting up netbase (4.37em1) ...
insserv: Service mountkernfs has to be enabled to start service
networking insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing netbase (--configure):
 subprocess installed post-installation script returned error exit
status 1

debootstrap handles this differently by configuring packages in steps but
this is not workable for the cross-install mechanism needed by multistrap.

multistrap downloads and extracts all .deb files and then runs a single
'dpkg --configure -a' run - with a cross-install, this is the only stage
to take place on the cross architecture.

Please add a 'Depends: initscripts' so that dpkg can work out that initscripts
has to be configured before netbase can be configured.

Thanks.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages netbase depends on:
ii  lsb-base                      3.2-23     Linux Standard Base 3.2 init scrip

Versions of packages netbase recommends:
ii  ifupdown                      0.6.9      high level tools to configure netw

netbase suggests no packages.

-- no debconf information



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

Reply via email to