On Sun, 15 May 2022 16:15:16 +0000 "Wright, Randy (HPE Servers Linux)"
<[email protected]> wrote:
On Wed, 11 May 2022 09:11:21 -0700 "Milesa & Richard Griswold"
<[email protected]> wrote:
> sudo dpkg -i *.deb
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?
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
