uploads of new source packages can't close bugs

Source package uploads containing a Launchpad-Bugs-Fixed field in their .changes file close bugs, but of course they only close bug tasks on the relevant source package in the relevant distribution, since the bug might have many tasks some of which do not apply. This is all right and proper.

However, it does cause a small problem for bugs of the form "we need this new package to exist"; the MOTU team use bugs of this form to organise their work. Such bugs obviously can't be filed against the relevant source package, since it does not yet exist in the Launchpad database; they are therefore filed simply against "Ubuntu", with no source package. Even though the appropriate bug number is usually referenced in the changelog in such a way as to produce a Launchpad-Bugs-Fixed field, Soyuz does not close these bug tasks automatically when accepting the new source package, because they aren't filed on the source package.

It seems to me that this could be improved, perhaps with some slight heuristics. How about this rule:

  Uploads may close either bug tasks on the correct source package in the correct distribution, *or* bug tasks on the correct distribution but without any source package.

Since it is not normally possible to have bug tasks on both "Ubuntu" and "Ubuntu (sourcepackagename)" (although this does occasionally happen due to what I think are Launchpad bugs, but it isn't something the normal UI lets you do), this should be unambiguous; in the rare case where it might be ambiguous I think it would be fine to resolve the problem manually.