I just realized that the DHCPv6 failure that netplan's tests detect were already known in xenial's networkd tests; these tests got marked as "expected failure".
I started to backport individual networkd fixes, but this quickly became a frankensoftware which has never been tested in that form, and it would take prohibitively long to finish. Since 231, networkd development has slowed down considerably and it's by and large stable (judging by Debian bug reports a lot of people actually use it, and we did not get complaints since 231 any more). So in summary I think it is better to backport networkd 231 wholesale. In the running system it is completely independent of systemd and other tools (standalone binary), it has good test coverage, has been tried and tested in yakkety (unlike xenial when we did not yet use/support networkd), so IMHO the risk of this is lower than spending days on reengineering fixes on top of 229. The main noise of the backport is that this also requires backporting some common utility code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627641 Title: Backport netplan to xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
