Bug#922715: debbugs: b.d.o/release-critical/britney/testing-nr wrongly reports RC bugs when reported against two packages
On Tue, 19 Feb 2019, Paul Gevers wrote: > Britney is using RC bugs to determine if package may migrate from > unstable to testing. If an RC bug is only in unstable and not in > testing, the package is not allowed to migrate. However, in the above > case simplejson is listed in both > https://bugs.debian.org/release-critical/britney/testing-nr > and > https://bugs.debian.org/release-critical/britney/unstable-nr > > Can you please have a look at it? I wanted to mark the failure as > skiptest, because I expect the bug to be assigned to > json-schema-validator in 10 days from now, and was counting on the RC > bug to block simplejson from migrating. So this is a case where we're using the status of the bug (present in testing) and then reversing it to apply to all of the packages to which the bug is assigned. We don't really have a good way to state that a bug assigned to multiple packages should apply to the intersection of all of the versions/packages listed (which is what you're looking for) rather than the OR of all the versions/packages listed (which is what the BTS does by default). Hopefully that clears things up; I don't expect that I'll get around to adding the AND/OR feature to versions any time soon, so in the meantime I'd just file a separate bug if you want to be sure that a package doesn't transition if one of the set already has. -- Don Armstrong https://www.donarmstrong.com Do not handicap your children by making their lives easy. -- Robert Heinlein _Time Enough For Love_ p251
Bug#922715: debbugs: b.d.o/release-critical/britney/testing-nr wrongly reports RC bugs when reported against two packages
Package: debbugs Version: 2.6.0 Severity: normal X-Debbugs-CC: debian-rele...@lists.debian.org Hi Don, You may have noticed that I file a lot of bugs nowadays against two source packages due to autopkgtest failures in testing with one or more packages from unstable. Typically, I file them against the package that fails at the version in testing, while the package that breaks the test, will have it filed against the version in unstable. Yesterday, I raised the severity on several of them to serious. An example is bug 918632, which is filed against: simplejson/3.16.0-1 (in unstable) json-schema-validator/2.3.1-3 (in unstable and testing) Britney is using RC bugs to determine if package may migrate from unstable to testing. If an RC bug is only in unstable and not in testing, the package is not allowed to migrate. However, in the above case simplejson is listed in both https://bugs.debian.org/release-critical/britney/testing-nr and https://bugs.debian.org/release-critical/britney/unstable-nr Can you please have a look at it? I wanted to mark the failure as skiptest, because I expect the bug to be assigned to json-schema-validator in 10 days from now, and was counting on the RC bug to block simplejson from migrating. Paul signature.asc Description: OpenPGP digital signature
