| 2016-04-21 22:16:14 |
Paul Sladen |
bug |
|
|
added bug |
| 2016-04-21 22:17:00 |
Launchpad Janitor |
ubuntu: status |
New |
Confirmed |
|
| 2016-04-21 22:18:40 |
Paul Sladen |
bug |
|
|
added subscriber Neal Gompa |
| 2016-04-21 22:20:54 |
Paul Sladen |
description |
'/etc/init.d/networking' for 'ifupdown' starts with:
# 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/
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.
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. |
'/etc/init.d/networking' for 'ifupdown' starts with:
# 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/
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.
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. |
|
| 2016-04-21 22:28:44 |
Paul Sladen |
description |
'/etc/init.d/networking' for 'ifupdown' starts with:
# 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/
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.
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. |
'/etc/init.d/networking' for 'ifupdown' starts with:
# 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/<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/
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.
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. |
|
| 2016-04-22 04:32:38 |
Ubuntu Foundations Team Bug Bot |
tags |
regression-release |
bot-comment regression-release |
|
| 2016-04-22 04:49:11 |
Neal Gompa |
affects |
ubuntu |
ifupdown (Ubuntu) |
|
| 2016-04-22 13:40:32 |
Paul Sladen |
ifupdown (Ubuntu): status |
Confirmed |
Won't Fix |
|
