Your message dated Fri, 9 Nov 2007 00:14:33 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450367: xblast-tnt-sounds: debian/watch fails to report
upstream's version
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 ---
Source: xblast-tnt-sounds
Version: 20040429-2
Severity: minor
Usertags: dehs-no-upstream
Hello maintainer,
The debian/watch file of your package on the unstable distribution fails to
report upstream's version.
Uscan's message follows:
----
uscan warning: In /tmp/xblast-tnt-sounds_watchgzrIBX,
no matching hrefs for watch line
http://heanet.dl.sourceforge.net/sourceforge/xblast/
sounds-([\d-]+)\.tar\.gz debian uupdate
----
Please note that this message is auto-generated by extracting the information
from the Debian External Health Status (a.k.a. DEHS) no_upstream page[1].
At the moment of running the package version found is the one indicated in the
report.
If you have already fixed this issue please ignore and close this report.
If you belive this message can be improved in any way don't hesitate to contact
me
by replying to [EMAIL PROTECTED] (where NNNNN is the number of this bug
report).
If you wish not to be notified in the future contact me so I add you to the
ignore list.
[1] http://dehs.alioth.debian.org/no_upstream.html
Kind regards, Raphael Geissert.
--- End Message ---
--- Begin Message ---
> On 07/11/2007, Gerfried Fuchs <[EMAIL PROTECTED]> wrote:
> > That's right, because the only package upload so far was unversioned.
> > Further releases of the package will though match the watchfile so it is
> > correctly set for when this might happen.
>
> Could you please keep this report open and close it when the new
> package is uploaded to the archive?
No, I don't want to keep bogus bug reports opened against my packages,
sorry.
> That way my scripts are able to keep track of the status of a given
> package and prevent an other report against the same package to be
> filed.
That way I will stumble upon the bugreport that is no bug again and
again, preventing me from noticing bugreports that really are such
things. Please keep track of bogus reports in a different way.
So long,
Rhonda
--- End Message ---
