Your message dated Fri, 22 Jan 2010 21:02:59 +0100
with message-id <20100122200258.gb23...@lisa>
and subject line Invalid bug
has caused the Debian Bug report #449813,
regarding vimoutliner: debian/watch fails to report upstream's version
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 [email protected]
immediately.)
--
449813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449813
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: vimoutliner
Version: 0.3.4-8
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 watchfile /tmp/vimoutliner_watch9iCDyM, reading webpage
http://www.vimoutliner.org/files/ failed: 403 Forbidden
----
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 ---
The package currently does not have a proper watch file, as
upstream does not provide an appropriate download infrastructure.
Instead it contains a comment in it, stating that its currently
not possible. So I cannot really do something about this bug.
--- End Message ---
