ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
'/etc/init.
# Required-Start: mountkernfs $local_fs urandom
it would appear that 'mountkernfs' and 'urandom' are not hard-dependencies, and their presence prevents successful installation in virtual machines in some circumstances. This was reported by Neal Gompa/<
http://
Full and snipped output logs are at:
http://
https:/
in particular:
[ 530s] [239/256] installing ifupdown-
[ 530s] Creating /etc/network/
[ 531s] insserv: Service mountkernfs has to be enabled to start service networking
[ 531s] insserv: Service urandom has to be enabled to start service networking
[ 531s] insserv: exiting now!
[ 531s] update-rc.d: error: insserv rejected the script header
[ 531s] dpkg: error processing package ifupdown (--install):
[ 531s] subprocess installed post-installation script returned error exit status 1
The reporter tested that commenting out 'mountkernfs' and 'urandom' allowed the ifupdown '/etc/init.
Ideally a hard-dependency should not be declared if it is not actually a hard-dependency, and introduces a regression by preventing successfully installation in circumstances that are reported to have worked previously for installing earlier Debian/Ubuntu versions on OBS.
description: | updated |
description: | updated |
affects: | ubuntu → ifupdown (Ubuntu) |
Status changed to 'Confirmed' because the bug affects multiple users.