Version: 2:2.10-8~bpo11+1



Hello,


The version of wpasupplicant (2:2.10-8~bpo11+1) in bullseye-backports is incompatible with network-manager (currently 1.30.0-2 in bullseye, no backports package available) which creates an unmet dependency issue when trying to install network-manager, which in turn is creating the following issue:

 wpasupplicant : Breaks: network-manager (< 1.36.4-2~) but 1.30.0-2 is going to be installed

This bug affects two of my computers, a desktop workstation connected via
Ethernet and a laptop connected via Wi-Fi.  When I updated the computers, I
didn't pay close enough attention to what Apt was doing until it had
already removed Network Manager.  I was able to reinstall Network Manager
on the workstation as follows:

sudo sh -c 'echo nameserver 8.8.8.8 > /etc/resolv.conf'
sudo apt install wpasupplicant=2:2.9.0-21
sudo apt install network-manager-gnome
sudo apt-mark hold wpasupplicant=2:2.9.0-21

2:2.9.0-21 is the current non-backports version of wpasupplicant for
Bullseye.  Since Wi-Fi wasn't working on the laptop, I plugged a USB flash
drive into the workstation, changed to the directory where the USB flash
drive was mounted, and downloaded the required packages using this command:

apt download \
network-manager \
network-manager-gnome \
wpasupplicant \
libbluetooth3 \
libndp0 \
libteamdctl0

I then moved the USB flash drive to the laptop, changed to the directory
where the USB flash drive was mounted, and ran these commands:

sudo dpkg -i *.deb
sudo apt-mark hold wpasupplicant=2:2.9.0-21

At that point Network Manager was working again on both computers.  Once
this issue is resolved, the hold on wpasupplicant can be removed by running:

sudo apt-mark unhold wpasupplicant

Me too.

I had a similar experience to that related in comment 10, requiring
re-installation of  network-manager and dependencies from .deb files.
Due to the dependency problem between wpasupplicant and network-manager,
removing network-manager may be offered as a mitigation by apt and
accepted without consideration of the consequences.    And if that
happens, transferring the .deb files needed to correct the issue from
another system may be necessary.   Another approach on a relatively
simple network may be to configure networking with manual tools such as
ip, ifconfig, and route, after which recovery with apt can be effected.

In light of the severe consequences that may be encountered, is
it possible that the 2:2.10-8-bpo11+1 version of wpasupplicant
can be be removed from bullseye-backports until the required
network-manager version can be added?

On Sun, 15 May 2022 16:15:16 +0000 "Wright, Randy (HPE Servers Linux)" <rwright@hpe.com> wrote:

The patch to automatically enable WPA3 mode in NetworkManager is
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/759

Which means, it is not part of 1.30.0-2 as found in bullseye.

So, I think the best option is, if wpasupplicant simply drops the
versioned Breaks against network-manager from the bpo upload.

The versioned Breaks was mainly for users of unstable/bookworm, to
ensure they don't have a non-working combination installed.

Regards,
Michael

Hi,

Indeed, it should not be a big issue then. OTOH I have uploaded NM to backports (currently sitting in NEW).
Michael, if you disagree with the backport, please let the backports team know — or I can ask for a reject myself.

Am 16.05.2022 um 10:35 schrieb Andrej Shadura:

If you have tested, that the backport works fine on bullseye, then I
don't have any objectsions.

It would be great if you could push your changes to a
debian/bullseye-backports branch (including a git tag), which I can pull
into my repo.

Michael

Hi,

I’ve only tested it by installing it on my home server, so I guess it tested the Ethernet and bridge functionality.

https://salsa.debian.org/andrewsh/network-manager/-/tree/debian/bullseye-backports

Am 16.05.22 um 11:01 schrieb Andrej Shadura:

Thanks a lot!

Am 16.05.22 um 11:01 schrieb Andrej Shadura:

Thank you!