[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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


Reply to: