Control: tags -1 + moreinfo
On Tue, 20 Jun 2017 09:05:46 +0530 shirish शिरीष wrote: [...] > Dear Maintainer, Hello shirish, thanks for your bug report, which, however, is not very clear. > While I have seen the above being exhibited by wpagui only, there may > be other packages which might be affected by the above. See the whole > discussion starting from > https://lists.debian.org/debian-release/2017/06/msg00487.html to see > what apt-listbugs shows and what the reality is. I cannot find much of a discussion there (maybe I am just a bit sleepy now...). Anyway, could you please clarify which bug reports you believe is incorrectly shown by apt-listbugs? The three bug reports mentioned in the message you referred to seem to show up when querying the BTS for bugs affecting the version currently in stable, testing, and unstable of wpasupplicant: $ apt-listbugs list wpasupplicant/2:2.4-1 Retrieving bug reports... Done Parsing Found/Fixed information... Done grave bugs of wpasupplicant (→ 2:2.4-1) <Outstanding> b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the (network-manager) list available. serious bugs of wpasupplicant (→ 2:2.4-1) <Outstanding> b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi b3 - #849875 - broadcom-sta-dkms: Wifi association took too long, failing activation Summary: wpasupplicant(3 bugs) However, they all seem to be found in version 2.6-2 which is now superseded by versions with epoch 2. What seems to have happened (see the [tracker page]) is that the upstream version 2.4 was reintroduced into unstable (with epoch 2) and then migrated to stretch. [tracker page]: <https://tracker.debian.org/pkg/wpa> Hence, I would say that those three bugs only affect experimental and are not in stretch, buster or sid. Please write to the wpasupplicant maintainers and ask for confirmation that those three bugs should be marked as found in wpa/2:2.6-2 and not in wpa/2.6-2 (otherwise the BTS version tracking will continue to incorrectly think that the bugs affect stable, testing, unstable, and experimental). Please let me know whether my guess is correct. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpz3eZgLCIf_.pgp
Description: PGP signature
