Your message dated Fri, 30 Jun 2006 07:32:09 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#373485: fixed in pybluez 0.7.1-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: pybluez
Version: 0.6.1-2
Severity: important


  Hi, your package has been detected as generating a python
module/extension that may need an upgrade to the new Python Policy[1].

  A wiki page [2] explains what has to be done to upgrade your packages
to the new Policy. This bug may be a false positive, in that case,
please just close the bug.

  This bug is part of a mass bug filling, and its severity will be
raised to serious when python will default to python2.4. Please note
that this bug (even not being RC) falls under the 0-day NMU policy.


  [1] http://lists.debian.org/debian-devel-announce/2006/06/msg00009.html
  [2] http://wiki.debian.org/DebianPython/NewPolicy




--- End Message ---
--- Begin Message ---
Source: pybluez
Source-Version: 0.7.1-2

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

pybluez_0.7.1-2.diff.gz
  to pool/main/p/pybluez/pybluez_0.7.1-2.diff.gz
pybluez_0.7.1-2.dsc
  to pool/main/p/pybluez/pybluez_0.7.1-2.dsc
pybluez_0.7.1.orig.tar.gz
  to pool/main/p/pybluez/pybluez_0.7.1.orig.tar.gz
python-bluez_0.7.1-2_powerpc.deb
  to pool/main/p/pybluez/python-bluez_0.7.1-2_powerpc.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.
Filippo Giunchedi <[EMAIL PROTECTED]> (supplier of updated pybluez 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: Thu, 15 Jun 2006 15:37:57 +0200
Source: pybluez
Binary: python-bluez
Architecture: source powerpc
Version: 0.7.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Bluetooth <[EMAIL PROTECTED]>
Changed-By: Filippo Giunchedi <[EMAIL PROTECTED]>
Description: 
 python-bluez - Python wrappers around BlueZ for rapid bluetooth development
Closes: 373485
Changes: 
 pybluez (0.7.1-2) unstable; urgency=low
 .
   * migration to new python policy, I hope to have got this right!
     (Closes: #373485)
   * build-depend on libbluetooth-dev not libbluetooth1-dev
 .
 pybluez (0.7.1-1) unstable; urgency=low
 .
   * New upstream release
Files: 
 b3180e4acd26a694718798f44ad414d8 766 python optional pybluez_0.7.1-2.dsc
 c825831df7df32ce7720dfc4ead7ba50 2569 python optional pybluez_0.7.1-2.diff.gz
 af8b541f31207057c2b558330944cebf 90696 python optional 
python-bluez_0.7.1-2_powerpc.deb
 7cc4cc7317feb6c4ebae791c9baa8208 59612 python optional 
pybluez_0.7.1.orig.tar.gz

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

iD8DBQFEpTJ1ABzeamt51AERAoDZAJ9g8EPLHU29cUdZru3iVg3UPahngACeNfCX
FAhmvsVY0HPMeGXJ6kCnRB0=
=3+lF
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to