Bug#1010775: wpasupplicant 2:2.10-8~bpo11+1 in bullseye-backports creates an unmet dependency issue with network-manager 1.30.0-2 in bullseye

2022-05-20 Thread Michael Biebl
Am 16.05.22 um 11:01 schrieb Andrej Shadura: 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 Thank you!

Bug#1010775: wpasupplicant 2:2.10-8~bpo11+1 in bullseye-backports creates an unmet dependency issue with network-manager 1.30.0-2 in bullseye

2022-05-16 Thread Michael Biebl
Am 16.05.22 um 11:01 schrieb Andrej Shadura: 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

Bug#1010775: wpasupplicant 2:2.10-8~bpo11+1 in bullseye-backports creates an unmet dependency issue with network-manager 1.30.0-2 in bullseye

2022-05-16 Thread Andrej Shadura
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 + "Wright, Randy (HPE Servers Linux)" In light of the severe consequences that may

Bug#1010775: wpasupplicant 2:2.10-8~bpo11+1 in bullseye-backports creates an unmet dependency issue with network-manager 1.30.0-2 in bullseye

2022-05-16 Thread Michael Biebl
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 + "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

Bug#1010775: wpasupplicant 2:2.10-8~bpo11+1 in bullseye-backports creates an unmet dependency issue with network-manager 1.30.0-2 in bullseye

2022-05-16 Thread Andrej Shadura
Hi, On Mon, 16 May 2022, at 10:31, Michael Biebl wrote: > On Sun, 15 May 2022 16:15:16 + "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

Bug#1010775: wpasupplicant 2:2.10-8~bpo11+1 in bullseye-backports creates an unmet dependency issue with network-manager 1.30.0-2 in bullseye

2022-05-16 Thread Michael Biebl
On Sun, 15 May 2022 16:15:16 + "Wright, Randy (HPE Servers Linux)" wrote: On Wed, 11 May 2022 09:11:21 -0700 "Milesa & Richard Griswold" 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

Bug#1010775: wpasupplicant 2:2.10-8~bpo11+1 in bullseye-backports creates an unmet dependency issue with network-manager 1.30.0-2 in bullseye

2022-05-15 Thread Wright, Randy (HPE Servers Linux)
On Wed, 11 May 2022 09:11:21 -0700 "Milesa & Richard Griswold" 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

Bug#1010775: wpasupplicant 2:2.10-8~bpo11+1 in bullseye-backports creates an unmet dependency issue with network-manager 1.30.0-2 in bullseye

2022-05-11 Thread Milesa & Richard Griswold
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

Bug#1010775: wpasupplicant 2:2.10-8~bpo11+1 in bullseye-backports creates an unmet dependency issue with network-manager 1.30.0-2 in bullseye

2022-05-09 Thread Miga
Package: wpasupplicant 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