Reporting a bug against a binary package that only exists on d-ports
architectures (such as libgcc2 which is m68k-specific) fails, the
report gets assigned to unknown-package@qa.debian.org instead of GCC.

I could understand if this failed for cases where the *source* package
is also only in d-ports (unreleased, usually, then), such as is the
case for some of the bootloaders, but in my case here, the source
package is part of Debian proper and the list of binary packages that
this source package builds is discoverable, so failing here is not
amusing.