Hello Mathieu, or anyone else affected, Accepted nplan into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.10.1 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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! ** Also affects: nplan (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: nplan (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed-artful -- 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/1713142 Title: Backport netplan 0.32 Status in nplan package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in nplan source package in Zesty: Fix Committed Status in nplan source package in Artful: Fix Committed Bug description: [Impact] Backport features in upstream netplan / netplan in bionic to zesty, xenial. [Test cases] == Autopkgtests == Run autopkgtests, they should all pass. == MTU settings == 1) Set a MTU for a device managed by NetworkManager: ethernet: eth0: renderer: NetworkManager mtu: 1400 dhcp4: yes 2) Verify that the MTU is properly applied to the device. [Regression potential]Failure to properly configure existing interfaces for MTU settings, IPv6 settings would be regressions; for example, if existing network devices were to all get the same MTU, or the same MTU as another interface configured in netplan although the configuration is not set to apply to them (ie. the config bleeds to other devices); then this would be a regression. Any new failures in autopkgtests would also be regressions to be investigated as possibly caused by the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1713142/+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
