desktop-packages team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

Build logs:
amd64: https://launchpadlibrarian.net/216762484/buildlog_ubuntu-wily-amd64.network-manager_1.0.4-0ubuntu3~mtrudel4_BUILDING.txt.gz
armhf: https://launchpadlibrarian.net/216764146/buildlog_ubuntu-wily-armhf.network-manager_1.0.4-0ubuntu3~mtrudel4_BUILDING.txt.gz
ppc64el: https://launchpadlibrarian.net/216762499/buildlog_ubuntu-wily-ppc64el.network-manager_1.0.4-0ubuntu3~mtrudel4_BUILDING.txt.gz

I've picked these three as examples, but NM builds successfully on all
architectures.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1493934

Title:
  [FFE] NetworkManager 1.0.4

Status in network-manager package in Ubuntu:
  New

Bug description:
  NetworkManager 1.0.4 fixes a large number of potential bugs in
  handling network configurations, along with letting us be up to date
  with the current developments upstream (which has been an issue in
  previous releases, where NM had to be kept back due to requirements on
  the phone side). These requirements are not issues for the moment, so
  this release is the perfect time to update NM to a the current stable
  and recommended version.

  It's already in -proposed now, but had multiple issues in autopkgtests
  and some smaller issues with failures in unit tests which have so far
  caused it to be blocked in proposed.

  It has been tested for three weeks in various configurations,
  connecting to wifi (open, WPA2, WPA-Enterprise), ethernet, and VPNs
  (openvpn). It works properly in KDE and GNOME environments without
  changes to the UI components.

  Other NM components (VPNs, for example) continue to function as there
  have not been substancial changes to the API.

  Attached and linked are build logs, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1493934/+subscriptions