Your message dated Tue, 22 Aug 2006 08:02:02 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#384068: fixed in notify-python 0.1.0-2
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 ---
Package: python-notify
Version: 0.1.0-1
Severity: grave
python-notify 0.1.0-1 depends on python (<< 2.4), a version which is no
longer available in Unstable.
debian/pyversions lists only "2.3", but simply rebuilding on a system
with python 2.4.3-11 created a package depending on python (>= 2.4). Not
sure why; maybe a pyversions of just "2.3" is now invalid somehow?
The package so built appears to work fine (based on running the tests in
tests/) with python2.4, and I can't find any indication that the Galago
people think it won't work with 2.4 or above.
At any rate, the package needs either a pyversions tweak and a rebuild,
or a dependency on python2.3 instead of python.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages python-notify depends on:
ii libnotify1 0.4.0-1 sends desktop notifications to a n
ii python 2.4.3-11 An interactive high-level object-o
ii python-gtk2 2.8.6-5 Python bindings for the GTK+ widge
ii python-support 0.4.1 automated rebuilding support for p
python-notify recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: notify-python
Source-Version: 0.1.0-2
We believe that the bug you reported is fixed in the latest version of
notify-python, which is due to be installed in the Debian FTP archive:
notify-python_0.1.0-2.diff.gz
to pool/main/n/notify-python/notify-python_0.1.0-2.diff.gz
notify-python_0.1.0-2.dsc
to pool/main/n/notify-python/notify-python_0.1.0-2.dsc
python-notify_0.1.0-2_i386.deb
to pool/main/n/notify-python/python-notify_0.1.0-2_i386.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.
Gustavo Franco <[EMAIL PROTECTED]> (supplier of updated notify-python 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, 22 Aug 2006 11:47:56 -0300
Source: notify-python
Binary: python-notify
Architecture: source i386
Version: 0.1.0-2
Distribution: unstable
Urgency: low
Maintainer: Gustavo Franco <[EMAIL PROTECTED]>
Changed-By: Gustavo Franco <[EMAIL PROTECTED]>
Description:
python-notify - Python bindings for libnotify
Closes: 384068
Changes:
notify-python (0.1.0-2) unstable; urgency=low
.
* Fix debian/pyversions changing content from 2.3 to >= 2.3.
(Closes: #384068)
Files:
f7e7634ea8d713581f0211caad2d3a6a 828 python optional notify-python_0.1.0-2.dsc
c1f6be76a8349af084edd292b0a7f122 312756 python optional
notify-python_0.1.0.orig.tar.gz
4ac5d8d7c2820f9c6e0f588c35c5e1ef 1625 python optional
notify-python_0.1.0-2.diff.gz
e52a573939f5dc074b936a5fd98e2716 12602 python optional
python-notify_0.1.0-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE6xtI7ftwBTcVV3gRAlT0AKCxCyRz0nglElprS9aFIipGaLrZFwCeOpe4
zyCsGawkJ8+aFTTi9crbuR8=
=m75h
-----END PGP SIGNATURE-----
--- End Message ---
