Your message dated Tue, 11 Dec 2007 00:47:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#453544: fixed in workrave 1.8.5-4
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: workrave
Version: 1.8.5-3
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.pl warning: In /tmp/workrave_watchwvRyQT,
  no matching hrefs for watch line
  http://qa.debian.org/watch/sf.php?project=workrave workrave-([\d.]*).tar.gz
----

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 on the 
report.
If you have already fixed this issue please ignore and close this report.

If you believe 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 need help to fix this problem tag this bug with 'help'
 so I pay special attention to it when submitting patches.
This can be done by running % bts tag NNNNN help (where NNNNN is the the number 
of this bug report).

If you wish not to be notified in the future please 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 ---
Source: workrave
Source-Version: 1.8.5-4

We believe that the bug you reported is fixed in the latest version of
workrave, which is due to be installed in the Debian FTP archive:

workrave_1.8.5-4.diff.gz
  to pool/main/w/workrave/workrave_1.8.5-4.diff.gz
workrave_1.8.5-4.dsc
  to pool/main/w/workrave/workrave_1.8.5-4.dsc
workrave_1.8.5-4_amd64.deb
  to pool/main/w/workrave/workrave_1.8.5-4_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Francois Marier <[EMAIL PROTECTED]> (supplier of updated workrave package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 11 Dec 2007 13:29:54 +1300
Source: workrave
Binary: workrave
Architecture: source amd64
Version: 1.8.5-4
Distribution: unstable
Urgency: low
Maintainer: Francois Marier <[EMAIL PROTECTED]>
Changed-By: Francois Marier <[EMAIL PROTECTED]>
Description: 
 workrave   - Repetitive Strain Injury (RSI) prevention tool
Closes: 453544
Changes: 
 workrave (1.8.5-4) unstable; urgency=low
 .
   * Fix the watch file (closes: #453544)
   * Bump Standards-Version to 3.7.3 (no changes)
   * Remove /usr/sbin from debian/dirs (it was empty)
   * Add a call to dh_desktop in debian/rules
Files: 
 88c12fa7803f95be0e54afc2c37642a2 900 gnome optional workrave_1.8.5-4.dsc
 cb3177c1bfb37f443076af07ceedd26d 11754 gnome optional workrave_1.8.5-4.diff.gz
 62a7190807124d698e15999b66b59494 949562 gnome optional 
workrave_1.8.5-4_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHXdqDScUZKBnQNIYRAutHAJwL9VUFvPD+ovoyRF++2cqJDn94JQCgsg/r
aYVjj6BTqebrp/f/kyByJ6E=
=wys/
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to