group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1645698@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package network-manager - 1.2.6-0ubuntu1

---------------
network-manager (1.2.6-0ubuntu1) yakkety; urgency=medium

  * Rebase to upstream point release 1.2.6 (LP: #1645698)
  * Refreshing patches, dropped ones that are merged upstream:
    - wifi-clear-WiFi-requested_scan-if-suppl-exits.patch
    - wifi-clear-WiFi-requested_scan-if-suppl-goes-INACTIV.patch

 -- Aron Xu <happyaron@xxxxxxxxxx>  Tue, 20 Dec 2016 00:54:10 +0800

** Changed in: network-manager (Ubuntu Yakkety)
       Status: Fix Committed => Fix Released

-- 
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/1645698

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released

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.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [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/oem-priority/+bug/1645698/+subscriptions