The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1714933 Title: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names" Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Committed Status in systemd source package in Artful: Fix Released Bug description: [Impact] networkd cannot manage interface names with ':' in them. As used commonly, by convention, by other tools. [Fix] Update networkd validation routines and test-suites to accept network interface names with ':' in it. [Testcase] Create an inteface with ':' in its name and use it anywhere where systemd validates ifname. E.g. Socket BindToDevice definition, nspawn network zone info, Label= in [Address] section in networkd. [Regression Potential] This fix will change validation routines, and thus commands or settings that were previously rejected or ignored will now take effect. Specifically Label= settings in networkd may lead to networking conflicts. The justification for this change is that networkd should really use the sensible ':' ifnames that the user is requesting systemd to use. [Original Bug Reprot] PR: https://github.com/systemd/systemd/pull/5117 issue: https://github.com/systemd/systemd/issues/4057 Before the networkd from 231 was backported, it was possible to use interface alias names that contained a colon, e.g. eth0:1. This is commonly used to make legacy tools like "ifconfig" work, because they *expect* a colon in the interface name. Martin told me to file a bug for this. Merging networkd from 231 lead to a regression where valid configs were not accepted anymore after the backport. Please merge that fix for the regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
