Your message dated Wed, 26 Jun 2013 19:26:59 +0200
with message-id <[email protected]>
and subject line watch file updated in 0.21.1-1
has caused the Debian Bug report #691678,
regarding gaupol: 0.20 available upstream
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.)
--
691678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691678
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gaupol
Severity: wishlist
Dear Maintainer,
gaupol 0.20 is available upstream. Your watch file looks for tar.gz,
but starting with 0.20 new tarballs are released only as tar.xz.
And, for what it's worth, I use debian unstable myself and can say
that gaupol 0.20 should work fine with the current unstable. Maybe a
half a year ago there were still problems with pygobject upstream
and in debian's python 3 packaging, but that should all be ok now.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Source: gaupol
Source-Version: 0.21.1-1
ups, forgot to close this one in the changelog
--- End Message ---
