Your message dated Tue, 30 Oct 2012 06:26:15 +0000 with message-id <20121030062615.gc25...@master.debian.org> and subject line DDPO: comment-only 'debian/watch' reported as "Error" has caused the Debian Bug report #498108, regarding qa.debian.org: package with comment-only 'debian/watch' reported as "Error" 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.) -- 498108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: qa.debian.org Severity: normal Some packages do not have an upstream that can be checked. In many cases, such packages have a 'debian/watch' file consisting only of comments that explain why 'uscan' cannot be used for the package. The DEHS reports this as a package "without a checkable upstream", which is not an error. It also uses the comments in the 'debian/watch' file as the explanation. <URL:http://dehs.alioth.debian.org/maintainer.php?name=lojban-common> The QA package summary incorrectly lists "Error" for the package, linking to the DEHS report (which shows it as not an error). <URL:http://qa.debian.org/developer.php?packages=lojban-common> The QA package summary should, instead, report this situation indicating the upstream version is unknown, but *not* as an error. -- \ “Pinky, are you pondering what I'm pondering?” “Um, I think so, | `\ Brainie, but why would anyone want to Pierce Brosnan?” —_Pinky | _o__) and The Brain_ | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---This bug seems solved already. Feel free to reopen if you find examples illustrating that the bug is not yet fully solved.
--- End Message ---
