Hi, On Mon, 16 May 2022, at 10:40, Michael Biebl wrote: > Am 16.05.2022 um 10:35 schrieb Andrej Shadura: >> Hi, >> >> On Mon, 16 May 2022, at 10:31, Michael Biebl wrote: >>> On Sun, 15 May 2022 16:15:16 +0000 "Wright, Randy (HPE Servers Linux)" >>>> 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. >> >> 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. >> > > If you have tested, that the backport works fine on bullseye, then I > don't have any objectsions.
I’ve only tested it by installing it on my home server, so I guess it tested the Ethernet and bridge functionality. > 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. https://salsa.debian.org/andrewsh/network-manager/-/tree/debian/bullseye-backports -- Cheers, Andrej
