Hello ben, or anyone else affected, Accepted bind9 into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bind9/1:9.10.3.dfsg.P4-10.1ubuntu5.3 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-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. 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: bind9 (Ubuntu Zesty) Status: In Progress => Fix Committed ** Changed in: bind9 (Ubuntu) Status: Fix Committed => Fix Released ** Tags added: verification-needed verification-needed-zesty ** Changed in: bind9 (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1565060 Title: defaults file is ignored Status in bind9 package in Ubuntu: Fix Released Status in bind9 source package in Xenial: Fix Committed Status in bind9 source package in Yakkety: Won't Fix Status in bind9 source package in Zesty: Fix Committed Status in bind9 package in Debian: Fix Committed Bug description: [Impact] Server start up options set in /etc/default/bind9 via the OPTIONS variable are ignored. The fix is to have the systemd service file source that file and use the given OPTIONS value. This is already being done in Ubuntu Artful and higher. The fix here is the same. [Test Case] # install bind9 $ sudo apt install bind9 # start it up $ sudo service bind9 start # inspect the command line of the process: $ ps fxaw|grep named|grep -v grep 396 ? Ssl 0:00 /usr/sbin/named -f -u bind # edit /etc/default/bind9 and include "-4" to the OPTIONS value so it looks like this: # startup options for the server OPTIONS="-4 -u bind" # restart bind9 sudo service bind9 restart # inspect the process command line again. Only the fixed version of the package will include the newly added "-4" parameter: $ ps fxaw|grep named|grep -v grep 17891 ? Ssl 0:00 /usr/sbin/named -f -4 -u bind [Regression Potential] Administrators who have for some reason altered the defaults file with an incorrect value for OPTIONS might be surprised after this update, since now that file is actually parsed and if it's indeed incorrect, the service may fail to start. [Other Info] None at this time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1565060/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp