Your message dated Wed, 7 Nov 2007 09:08:06 +0530
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450244: jmagick: 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: jmagick
Version: 6.2.6-0-1
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/jmagick_watchMLKeBJ, reading webpage
  http://www.yeo.id.au/jmagick/ failed: 500 Can't connect to www.yeo.id.au:80 
(connect: timeout)
----

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 Tue, Nov 06, 2007 at 08:32:56PM -0600, Raphael wrote:
> > > uscan warning: In watchfile /tmp/jmagick_watchMLKeBJ, reading webpage
> > >   http://www.yeo.id.au/jmagick/ failed: 500 Can't connect to
> > www.yeo.id.au:80 (connect: timeout)
> > > ----
> >
> > Well, I just tried it, and it worked. You might haev tried it when the
> > server was down. Would you mind trying it again, please?
> 
> I'm currently investigating why that report was sent since I've setup
> an ignore-by-keyword system on the reporting script and timeout is one
> of the listed keywords.
> 
> I really apologise for this and all the other possible reports that
> shouldn't have been sent at all.

Well, I don't see why you should be apologetic! :-)

I am closing the bug, if you don't mind.

Thanks.

Kumar
-- 
Kumar Appaiah,
458, Jamuna Hostel,
Indian Institute of Technology Madras,
Chennai - 600 036


--- End Message ---
_______________________________________________
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Reply via email to