Ubuntu
network-manager package

Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main)

Bug #1958710 reported by Matthieu Baerts
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

There are some differences between versions from Debian and Ubuntu. A new version has been released a week ago.

Debian Changelog:

network-manager (1.34.0-2) unstable; urgency=medium

  * Demote wpasupplicant to Recommends.
    There are enough use cases for network-manager not involving Wi-Fi which
    justifies to make this dependency optional. (Closes: #919619, #980218)

 -- Michael Biebl <email address hidden> Tue, 18 Jan 2022 20:59:36 +0100

network-manager (1.34.0-1) unstable; urgency=medium

  * New upstream version 1.34.0
  * Rebase patches
  * Install nm-priv-helper service
  * Update symbols file for libnm0

 -- Michael Biebl <email address hidden> Fri, 14 Jan 2022 00:18:58 +0100

NM ChangeLog:

=============================================
NetworkManager-1.34
Overview of changes since NetworkManager-1.32
=============================================

* initrd: wait for both IPv4 and IPv6 with "ip=dhcp,dhcp6".
* core: better handle sd-resolved errors when resolving hostnames.
* nmcli: fix import WireGuard profile with DNS domain and address
  family disabled.
* ndisc: send router solicitations before expiry.
* policy: send earlier the ip configs to the DNS manager.
* core: support linking with LLD 13.
* wireguard: importing wg-quick configuration files with nmcli
  no longer sets a negative, exclusive "dns-priority". This plays
  better with common split DNS setups that use systemd-resolved.
  Adjust the "dns-priority" to your liking after import yourself.
* NetworkManager no longer listens for netlink events for traffic
  control objects (qdiscs and filters).
* core: add internal nm-priv-helper service for separating privileges
  and have a way to drop capabilities from NetworkManager daemon.
* bond: add support for setting queue-id of bond port.
* dns: support configuring DNS over TLS (DoT) with systemd-resolved.
* nmtui: add support for WireGuard profiles.
* nmcli: add aliases `nmcli device up|down` beside connect|disconnect.
* conscious language: Deprecate 'Device.Slaves' D-Bus property in favor of new
  'Device.Ports' property. Depracate 'nm_device_*_get_slaves()' in favor of
  'nm_device_get_ports()' in libnm.
* nmcli: invoking nmcli command without arguments will now show 'default'
  instead of null address in route4 or route6 section.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your report, do you plan to work on that merge or did you just want to point out that the package has update available (if so we do know and have reports about outdated packages so you can avoid manual work in the futur)

Revision history for this message
Matthieu Baerts (matttbe) wrote :

Hi Sebastien,

Sorry I didn't know your team was already tracking that.

I opened this issue because I was trying to find the root cause of random disconnections when using Ubuntu Jammy: is it NM/iwd/kernel?

I'm using 'iwd' and I noticed it was outdated: 1.15 while the latest version is 1.21 and available on Debian side. So I opened this issue: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1958711

While at it, I also opened this issue for NM because I was not sure if the merge were done by requests or not. I mean: even if a few people can see there is an update available, I don't know if someone will update it because (s)he is in charge of that or if everybody would think "someone will do that" but because there is no specific task, the update can be pending for a long time if you see what I mean :)

In the past, I had a similar issue with Git which was not updated for quite a while because a merge had to be done and nobody was really in charge of update it. I had to ask for an update on IRC. This time, I opened an issue: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1956773

Do you think I should better close these 3 issues (NM/iwd/git)? Should I find someone on IRC to look at that instead?

Revision history for this message
Sebastien Bacher (seb128) wrote :

It's always ok to report issues you would like to see fixed, I was just pointing out that we usually have other way to list packages that need to be rebased on Debian. For desktop we use https://people.canonical.com/~platform/desktop/versions/desktop-packages.html for example

Changed in network-manager (Ubuntu):
status: New → Triaged
Revision history for this message
Matthieu Baerts (matttbe) wrote :

Hi Sebastien,

Thank you for the link. Good to know this list is closely monitored by the Desktop team.

(Also "funny" that for "network-manager" package, the last stable upstream version is not reported: an issue with the "watch" file?)

I guess for Git, I will need to continue pinging someone on IRC, that's fine :)

Revision history for this message
Sebastien Bacher (seb128) wrote :

the definition of the serie we want to use is a manual process, it has been updated now

Jeremy Bícha (jbicha)
Changed in network-manager (Ubuntu):
status: Triaged → Fix Released
status: Fix Released → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager - 1.34.0-2ubuntu3

---------------
network-manager (1.34.0-2ubuntu3) jammy; urgency=medium

  * d/tests/control: Have nm.py autopkgtest Depend on wpasupplicant

 -- Jeremy Bicha <email address hidden> Mon, 07 Feb 2022 16:40:52 -0500

Changed in network-manager (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.