cannot close/invalidate bugtask on no-longer published source package

[Alexander Sack]

firefox-3.1 ubuntu source package was introduced in jaunty cycle, but also removed again because it was renamed to firefox-3.5.

I reassigned all bugs manually; however bug 317226 already has a firefox-3.5 target and setting the firefox-3.1 target to invalid fails complaining that the bug is already filed against firefox-3.5.

to reproduce:

1. open https://bugs.edge.launchpad.net/ubuntu/+source/firefox-3.5/+bug/317226
2. select "invalid" for the firefox-3.1 task and hit submit
3. observe that this operation fails and the source package field shows "firefox-3.5" with the following error: "This bug has already been reported on firefox-3.5 (ubuntu)."

[William Grant (wgrant)]

staging is woefully out of date, so it's not a good test, but I can add a firefox-3.5 task to the bug on staging and then change the firefox-3.1 task's status, as expected. I can't do that to the same bug on edge.

This looks like bug #81014, but that was fixed years ago.

[William Grant (wgrant)]

Now I see there is one important difference between the staging and production databases - firefox-3.1 is still published in Jaunty on staging.

Is guessPackageNames() not seeing it because it is no longer published anywhere in Ubuntu on production?

[Alexander Sack (asac)]

On Thu, Apr 16, 2009 at 10:08:00AM -0000, William Grant wrote:
> Is guessPackageNames() not seeing it because it is no longer published
> anywhere in Ubuntu on production?
>

Not sure if that was a question in my direction. If so, I can confirm
that it was completely removed from any archive (probably kind of
special because most packages at least stick in one release).

 - Alexander

[Robert Collins (lifeless)]

Note that you can delete the task, which actually is entirely appropriate. So this issue really shouldn't affect anyone.