user [email protected] usertag 544812 querybts thanks In doing a little more poking around, I see this is only an issue when using querybts on a source package. This may simply be an artifact of screen-scraping the BTS, but I'd have to do some tests with the BTS' SOAP interface to verify that.
It does make sense that the source-based view wouldn't show it since affects is usually used against a binary package. The downside to the default source-based view that querybts (used via reportbug) is that the user likely misses the bugs affecting the package against which the bug is being filed. One potential solution is to specifically query the binary package bug pages for the "affects" bugs, but that's a potential drastic increase in traffic to the BTS per reportbug invocation. The long-term goal of switching to SOAP would likely make this trivial. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
