Debian Bug report logs - #980250
debbugs: rc export not great for bugs assigned to multiple packages

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Paul Gevers <[email protected]>

To: Debian Bug Tracking System <[email protected]>

Subject: debbugs: rc export not great for bugs assigned to multiple packages

Date: Sat, 16 Jan 2021 19:22:58 +0100

[Message part 1 (text/plain, inline)]

Package: debbugs
Version: 2.6.1
Severity: normal

Hi Don, all,

As you're probably well aware, the Release team is using the exports [1]
from the bts to influence the migration of packages from unstable to
testing.

As you may be aware, I (and several others) have been filing a lot of
bugs regarding autopkgtest regressions [2]. As a regression in an
autopkgtest from package a, due to an upload of package b, may either
indicate something wrong with (the autopkgtest of) package a (the
version in testin), or with the new upload of b (in unstable). Hence, I
file these bugs against package a and b, with the version of a in
testing (which often is the same as in unstable) and the version of b in
unstable (which per definition is different than in testing).

However, currently this doesn't (always??) get listed on the excuses
page, because the export lists the bug for package b under both testing
and unstable.

Example case that's currently there: bug #980111, with

paul@mulciber ~ $ rmadison frr
frr        | 6.0.2-2+deb10u1 | stable         | source, amd64, arm64,
armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
frr        | 6.0.2-2+deb10u1 | stable-debug   | source
frr        | 7.4-1           | testing        | source
frr        | 7.4-1           | unstable       | source
frr        | 7.4-1           | unstable-debug | source
frr        | 7.4-1+b1        | testing        | amd64, arm64, armel,
armhf, i386, mips64el, mipsel, ppc64el, s390x
frr        | 7.4-1+b1        | unstable       | amd64, arm64, armel,
armhf, i386, mips64el, mipsel, ppc64el, s390x

and

paul@mulciber ~ $ rmadison pam
pam        | 1.1.8-3.1+deb8u2 | oldoldstable   | source
pam        | 1.1.8-3.6        | oldstable      | source
pam        | 1.3.1-5          | stable         | source
pam        | 1.3.1-5          | testing        | source
pam        | 1.4.0-2          | unstable       | source
pam        | 1.4.0-2          | unstable-debug | source

and

elbrus@respighi:~$ grep 980111  ~release/britney/state/rc-bugs-*
/home/release/britney/state/rc-bugs-testing:src:frr 980111,972767
/home/release/britney/state/rc-bugs-testing:src:pam 956355,980111
/home/release/britney/state/rc-bugs-unstable:src:frr 980111,972767
/home/release/britney/state/rc-bugs-unstable:src:pam 980111

I would expect that bug 980111 would only be listed for pam in the
unstable export.

Paul

[1] https://bugs.debian.org/release-critical/britney/${suite}-nr
[2]
https://bugs.debian.org/cgi-bin/[email protected]

[OpenPGP_signature (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.