my apologies if i seem a bit miffed, but after researching the bug, tracking the issue upstream, all the way to a 2.6.32-stable release, and including all that information in the original bug report, it appears my bug report wasn't even read as all i get is an automated message saying:
* i need to test the problem in the current maverick build, but maverick is using 2.6.35 (not lucid's 2.6.32), you're not going to backport the driver from 2.6.35 to 2.6.32 (as i already included a link to the patch), and i'm not going to upgrade from a recently released LTS (lucid) to an unreleased non-LTS to fix this well-documented problem. * i need to rebuild the kernel myself to help upstream debug the issue, but upstream is already aware of the issue (see linux-wireless email thread referenced in original bug report) and has even provided a patch (see git commit to 2.6.32-stable in original bug report). i would understand if this bug was undiagnosed, a fix was unknown, and/or upstream was unaware, but none of that is the case. instead all the work has been done and all ubuntu needs to do is prioritize the bug/patch and decide whether to include it in a future kernel package (or prove my research into the recent lucid proposed-update kernel package wrong due to ubuntu's lack of detail in the changelog and i'll test it). i will be happy to test a proposed-update to insure it fixes the problem, or if absolutely necessary to convince ubuntu to include the patch, then i'll build and test the kernel myself (current ubuntu kernel source + upstream patch), but i think it is a disservice to contributors to send them on unnecessary tangents (testing a daily build which doesn't even include the same kernel version and building an upstream kernel when upstream is fully aware of and has already resolved the problem) with an automated message. if ubuntu does not consider this upstream bug/patch important enough to include in a LTS release, then simply say such and avoid the automated, unnecessary user requests. nonetheless, thank you for maintaining the linux kernel package in ubuntu. -- ath5k: monitor/promiscuous mode broken with channel hopping https://bugs.launchpad.net/bugs/602795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
