If the swscanner developers had their own bugtracker, it would be useful to register it as a product for bugtracking purposes; but judging by their Web site, they don't.
On our demo server, I just successfully recorded bug 42775 as occurring in Debian -- by clicking "Also affects: Distribution...", choosing "Debian" as the distribution, and "swscanner" as the source package. This seems like what you really want to do.
So perhaps the problem here is that not only is Launchpad's use of "upstream" unfamiliar to people who don't work on distributions, it's not even familiar to people who do work on distributions and (arguably correctly) regard Debian as "upstream" for Ubuntu. This could be explained much better if bug 1334 was fixed. What do you think?
If the swscanner developers had their own bugtracker, it would be useful to register it as a product for bugtracking purposes; but judging by their Web site, they don't.
On our demo server, I just successfully recorded bug 42775 as occurring in Debian -- by clicking "Also affects: Distribution...", choosing "Debian" as the distribution, and "swscanner" as the source package. This seems like what you really want to do.
So perhaps the problem here is that not only is Launchpad's use of "upstream" unfamiliar to people who don't work on distributions, it's not even familiar to people who do work on distributions and (arguably correctly) regard Debian as "upstream" for Ubuntu. This could be explained much better if bug 1334 was fixed. What do you think?