** Description changed: '/etc/init.d/networking' for 'ifupdown' starts with: - # Required-Start: mountkernfs $local_fs urandom + # 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 Conan Kudo/<Pharaoh_Atem> on #ubuntu-devel whilst working on support for Suse Open Build System (OBS) to build Xenial packages: http://changelogs.ubuntu.com/changelogs/pool/main/i/ifupdown/ifupdown_0.8.10ubuntu1/changelog Full and snipped output logs are at: - http://paste.fedoraproject.org/358318/61266534/ - https://paste.fedoraproject.org/358315/66065146/ + http://paste.fedoraproject.org/358318/61266534/ + https://paste.fedoraproject.org/358315/66065146/ in particular: - [ 530s] [239/256] installing ifupdown-0.8.10ubuntu1 - [ 530s] Creating /etc/network/interfaces. - [ 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.d/networking' init-script to successfully complete. + [ 530s] [239/256] installing ifupdown-0.8.10ubuntu1 + [ 530s] Creating /etc/network/interfaces. + [ 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.d/networking' init-script to + successfully complete. 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 and are reported to have worked before. + installation in circumstances that are reported to have worked + previously for installing earlier Debian/Ubuntu versions on OBS.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
