Your message dated Sun, 25 Jan 2009 18:34:34 -0600
with message-id <497d05f5.010bca0a.183f.4...@mx.google.com>
and subject line Re: Bug#512953: [DEHS] wrong display: "Debian Version: 0.8-1
(mangled: 0.7-1)"
has caused the Debian Bug report #512953,
regarding [DEHS] wrong display: "Debian Version: 0.8-1 (mangled: 0.7-1)"
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 ow...@bugs.debian.org
immediately.)
--
512953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: normal
User: qa.debian....@packages.debian.org
Usertag: dehs
From this morning, after having uploaded 0.8-1 last night:
http://dehs.alioth.debian.org/report.php?package=tenace
* Name: tenace
o Pop Inst: 22
o Upstream Version: 0.7
o Source download: tenace-0.7.tar.gz
o Debian Version: 0.8-1 (mangled: 0.7-1)
o Last time checked: 2009-01-24 07:16:27
o Last time found up to date: 2009-01-24 07:16:27
o Tot Upstream Bugs: 0
o Avg days opened: 0
o Distrib: unstable
o Watch: view
o Uscan errors: No errors
o Copyright: view
Christoph
--
c...@df7cb.de | http://www.df7cb.de/
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Hi Christoph,
Christoph Berg wrote:
> Package: qa.debian.org
> Severity: normal
> User: qa.debian....@packages.debian.org
> Usertag: dehs
>
> From this morning, after having uploaded 0.8-1 last night:
>
[...]
Thanks for the report, I've just fixed the bug and made the changes live.
When doing a time-based update DEHS was not checking the packages that were
updated causing the results you saw (i.e. knowing about the latest version in
unstable but not knowing the latest version by upstream; the mangled Debian
version was the old one because it is calculated when the watch file is
checked, and the up-to-date status was the previous one as well, which in this
case happened to be the truth).
Packages left in that status were being picked up by the daily new packages
update/run, making the bug more or less imperceptible.
Note: a similar bug exists for packages without watch files, but I don't feel
like fixing it as it requires a bit more of work that should better be spent on
DEHS2.
Cheers,
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
--- End Message ---
