* Steve Langasek <vor...@debian.org>, 2015-08-22, 22:17:
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.
Is BTS version tracking documented in details anywhere?
--
Jakub Wilk
