On Aug 22 2015, Steve Langasek <vor...@debian.org> wrote: > On Sat, Aug 22, 2015 at 09:54:10PM -0700, Nikolaus Rath wrote: >> Hello, > >> I'm struggling to understand the testing excuses for s3ql at >> https://qa.debian.org/excuses.php?package=s3ql. Among other things, it >> says: > >> * s3ql (source, amd64, i386, arm64, armel, armhf, mips, mipsel, powerpc, >> ppc64el, s390x) has new bugs! >> * Updating s3ql introduces new bugs: #792685 > >> However, the s3ql version in unstable is only affected by one bug >> (#771969), and that bug also affects the versions in stable and (before >> removal) testing: >> https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=s3ql > >> Why does britney think that migrating s3ql would introduce bugs? > > Because you marked bug #792685 fixed in a non-existent version. You need to > mark the bug fixed in the version that actually fixes it, or else do an > un-versioned close.
Oh, ok. My intention was to use the upstream version in which it was
fixed. I was assuming the BTS would infer that it has been fixed in any
debian version based on that one (or a newer one).
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
signature.asc
Description: PGP signature
