Package: bugs.debian.org Severity: normal X-Debbugs-Cc: t...@mirbsd.de 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-pack...@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. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init)
