Your message dated Sat, 15 Dec 2007 22:59:50 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#453705: PTS says wrongly "package has new bugs"
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
package: qa.debian.org
Hi,
http://packages.qa.debian.org/o/olsrd.html currently says:
out of date on sparc: olsrd, olsrd-plugins (from 0.5.4-1)
olsrd (source, i386, alpha, amd64, arm, hppa, ia64, mips, mipsel, powerpc,
s390, sparc) has new bugs!
Updating olsrd introduces new bugs: #452100
Which is wrong, because 452100 is in 0.5.4-1, which is available everywhere
except for sparc. "olsrd (sparc) has new bugs!" would be right.
regards,
Holger
Package olsrd
lenny (testing) (net): optimized link-state routing daemon (unik-olsrd)
0.5.3-3: alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 sparc
sid (unstable) (net): optimized link-state routing daemon (unik-olsrd)
0.5.4-2: alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390
0.5.4-1: sparc
pgpHKxGg0BL9Q.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Re: Holger Levsen 2007-11-30 <[EMAIL PROTECTED]>
> http://packages.qa.debian.org/o/olsrd.html currently says:
>
> out of date on sparc: olsrd, olsrd-plugins (from 0.5.4-1)
> olsrd (source, i386, alpha, amd64, arm, hppa, ia64, mips, mipsel, powerpc,
> s390, sparc) has new bugs!
> Updating olsrd introduces new bugs: #452100
>
> Which is wrong, because 452100 is in 0.5.4-1, which is available everywhere
> except for sparc. "olsrd (sparc) has new bugs!" would be right.
Hi,
that's not a PTS bug, the PTS merely shows information it gets
elsewhere. I suspect there's been a timing issue with britney getting
up to date information from the archive and/or the BTS.
I'm closing the bug as there's nothing we could fix. If someone has a
good idea where to reassign it, please reopen and do so, though.
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
--- End Message ---
