[Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release
Jeremy Bicha
jeremy at bicha.net
Wed Jan 18 05:30:23 UTC 2017
** Description changed:
[Impact]
This SRU would try to have the latest well-tested upstream point release
(1.2.6) of 1.2.x land in Xenial, which is the successor of the current
1.2.2 version, fixing quite some bugs that's suitable to land in the
stable branch.
https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2
[Test Case]
After installing the updated version, users should be able to avoid some
mem leaks in some cases and have generally improved DNS related
experiences.
[Regression Potential]
This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
complete.
+
+ [Other Info]
+ The first attempt at SRUing this to xenial was for 1.2.4 but it failed verification. This second attempt matches yakkety with 1.2.6.
+
+ Parallel building was enabled in xenial to keep the diff between xenial
+ and yakkety minimal since they are basically in sync now. Parallel
+ building was enabled in the yakkety package in May 2016 so it's been
+ working fine for a while.
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1645698
Title:
[SRU] Upgrade network-manager to latest point release
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
Triaged
Status in network-manager source package in Yakkety:
Fix Committed
Bug description:
[Impact]
This SRU would try to have the latest well-tested upstream point
release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
current 1.2.2 version, fixing quite some bugs that's suitable to land
in the stable branch.
https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2
[Test Case]
After installing the updated version, users should be able to avoid
some mem leaks in some cases and have generally improved DNS related
experiences.
[Regression Potential]
This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
complete.
[Other Info]
The first attempt at SRUing this to xenial was for 1.2.4 but it failed verification. This second attempt matches yakkety with 1.2.6.
Parallel building was enabled in xenial to keep the diff between
xenial and yakkety minimal since they are basically in sync now.
Parallel building was enabled in the yakkety package in May 2016 so
it's been working fine for a while.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+subscriptions
More information about the Ubuntu-sponsors
mailing list