Hello Newton, or anyone else affected, Accepted ubiquity into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/2.21.63.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: netcfg (Ubuntu Yakkety) Status: Fix Committed => Won't Fix ** Changed in: ubiquity (Ubuntu Xenial) Status: Triaged => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1646585 Title: oem-config replaces /etc/resolv.conf symlink with a hard file Status in Nvidia: New Status in netcfg package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in netcfg source package in Xenial: Fix Released Status in ubiquity source package in Xenial: Fix Committed Status in netcfg source package in Yakkety: Won't Fix Status in netcfg source package in Zesty: Fix Released Status in ubiquity source package in Zesty: Fix Released Bug description: [Impact] This breaks oem-config installs because after running oem-config-firstboot, /etc/resolv.conf's symlink might be replaced by a regular file. [Test case] The DGX server install process uses oem-config to setup certain settings. We are seeing that oem-config-firstboot is replacing the /etc/resolv.conf symlink to /run/resolvconf/resolv.conf with a hard file at /etc/resolv.conf. This was confirmed by booting in single user mode after a fresh install, and seeing the symlink is still there. Then go thru oem- config-firstboot, and find that the symlink is no longer there when that is done. We have to run "sudo dpkg-reconfigure resolvconf" to restore that symlink. [Regression potential] This may regress by failing to recognize a case where resolvconf is not in use, or triggering a false-positive (resolvconf is not in use, by an install is tricked into thinking it is and removes resolv.conf). Corruption of /etc/resolv.conf or /run/resolvconf/resolv.conf should be considered as possible regressions from this SRU. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1646585/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : [email protected] Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
