On Fri, May 10, 2013 at 10:23:04AM -0400, Jon Bernard wrote:
This is a bug report against liburcu/0.7.4-1 but you seem to have closed
it in an ltt-control upload. If it wasn't a liburcu bug in the first
place, you should have reassigned the bug before closing it; if it is a
liburcu bug OTOH, you shouldn't Close it from a different package.
From what I can see, the bug is still considered by britney for
migrations. You should either fix it, or mark notfound liburcu/0.7.4-1 &
found ltt-control/$brokenversion as to fix this inconsistency.
I don't completely follow, can you give some clarification? Also, can you
include a link to where I can see the britney information you're
referencing?
This bug report was originally "found" on liburcu/0.7.4-1. The
ltt-control upload send a mail to 688779-close@ and this marked the bug
as "fixed" in ltt-control/2.1.0~rc4-2. But it wasn't found on that
package in the first place, so this was essentially no-op. You can see
this on the top of this bug report:
Found in version liburcu/0.7.4-1
Fixed in version ltt-control/2.1.0~rc4-2
Since the bug was found in a version of liburcu and wasn't fixed (or
unfound) in subsequent liburcu version, the BTS considers the bug as
still present in the most recent version of liburcu. You can
clearly see this on the dot graph in the top right side of the bug page.
You can also see how this will prevent the migration of liburcu to
testing (britney's excuses):
http://qa.debian.org/excuses.php?package=liburcu
The solution is to either mark the bug as fixed in a newer version of
liburcu (by mailing -done@ with e.g. Version: 0.7.6-1) or to inform
control@:
notfound liburcu/0.7.4-1
found ltt-control/2.1.0~rc4-1
thanks
Cheers,
Faidon
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
