Thanks Lucas for your explanations, and I've now learned a new tool :) (rmadison)
Also after a second look to the graph I understand it better. > On 23/08/10 at 16:58 +0200, xavier grave wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi, >> >> The graph in the top right corner show that #571191 is fixed in testing >> and unstable, so what can I do that the DDPO don't trig in future on >> closed bug in music123 ? >> >> Thanks in advance for any answer, cordially, xavier grave > > Bonjour Xavier, > > As you can see in the graph in the top-right corner, the BTS still sees > #571191 as affecting unstable. > > $ rmadison music123 > music123 | 15-0.2 | stable | source, alpha, amd64, hppa, i386, ia64, mips, > mipsel, powerpc, s390, sparc > music123 | 15-0.2 | unstable | source, alpha > music123 | 16.2-2 | testing | source, amd64, armel, hppa, i386, ia64, > kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc > music123 | 16.2-2 | unstable | source, amd64, armel, hppa, i386, ia64, > kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc > > music123 15-0.2 (which is affected by the bug) is still present in unstable on > alpha according to rmadison. However, according to > https://buildd.debian.org/pkg.cgi?pkg=music123, 16.2-2 is "installed" on > alpha. > > This is a strange case of DB corruption or something. I've asked > #debian-release for a binNMU on alpha. Once the package is built, it should > make the problem disappear. > > - Lucas > -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
