Bug#565219: marked as done (qa.debian.org: bug history graphs are incorrect)
Your message dated Wed, 20 Jan 2010 09:23:55 +0100
with message-id <20100120082355.GB12193@rivendell>
and subject line Re: Bug#565219: qa.debian.org: bug history graphs are incorrect
has caused the Debian Bug report #565219,
regarding qa.debian.org: bug history graphs are incorrect
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
565219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565219
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: normal
Hi!
The bug count (and consequently the plot shape) is often incorrect
in the bug history graphs.
Consider for instance:
http://packages.qa.debian.org/d/dpkg-ruby.html
The package currenty has 0 (zero) outstanding bugs and 8 unarchived
resolved bugs.
Nonetheless, the graph
http://people.debian.org/~glandium/bts/d/dpkg-ruby.png
claims a total of 7 bugs and the plot is somehow missing in the last
days.
By looking at
http://people.debian.org/~glandium/bts/d/
I see that the graph was last updated on 13-Jan-2010 12:07,
but at that time, all bugs were already resolved.
I don't know whether this problem is related to (or even the same as)
bugs #546676, #548009, and #526237.
Anyway, please fix the generation of the graphs: they are nice, but
often misleading...
Thanks for your time.
--- End Message ---
--- Begin Message ---
On Wed, 20 Jan 2010, Francesco Poli wrote:
> If I understand correctly, the problem I reported is now fixed: as a
> consequence, I think this bug report may be safely closed as fixed.
Doing so with this mail.
Cheers,
--
Raphaël Hertzog
--- End Message ---
Reply to: