Your message dated Fri, 16 Jun 2006 16:02:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#373504: fixed in pyspf 1.6-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 ---
Package: pyspf
Version: 1.6-3
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: pyspf
Source-Version: 1.6-4

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

pyspf_1.6-4.diff.gz
  to pool/main/p/pyspf/pyspf_1.6-4.diff.gz
pyspf_1.6-4.dsc
  to pool/main/p/pyspf/pyspf_1.6-4.dsc
python-spf_1.6-4_all.deb
  to pool/main/p/pyspf/python-spf_1.6-4_all.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 pyspf 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 11:46:19 -0300
Source: pyspf
Binary: python-spf
Architecture: source all
Version: 1.6-4
Distribution: unstable
Urgency: low
Maintainer: Gustavo Franco <[EMAIL PROTECTED]>
Changed-By: Gustavo Franco <[EMAIL PROTECTED]>
Description: 
 python-spf - sender policy framework (SPF) module for Python
Closes: 373504
Changes: 
 pyspf (1.6-4) unstable; urgency=low
 .
   * debian/control:
     - Remove pabs from Uploaders field as requested.
     - Move architecture indep dependencies from Build-Depends
       to Build-Depends-Indep.
   * debian/rules:
     - Add simple-patchsys support without patches.
     - Remove unneded clean target.
 .
   * New Python Policy Changes: (Closes: #373504)
     + debian/control:
       - Bump up cdbs dependency to >= 0.4.41.
       - Bump up debhelper compatibility to 5.
       - Add python-support >= 0.2.3 dependency.
       - Add XS-Python-Version field.
       - Depends on ${python:Depends} and not on python2.3.
       - Add XB-Python-Version field.
     + debian/rules:
       - Add DEB_PYTHON_SYSTEM=pysupport
       - Remove echo call since cdbs take care about this.
       - Call python-distutils class after debhelper now.
     + debian/postinst && debian/prerm:
       - Remove "hand made" python-support stuff, cdbs does this.
Files: 
 11ba7dfc512959a55f5a7cbd68e2c3f2 803 python extra pyspf_1.6-4.dsc
 7625305ec3ed1c395b614bd7a5ba6ba6 2088 python extra pyspf_1.6-4.diff.gz
 26ce779a7ca70aa71dbd9d5fefb73287 9964 python extra python-spf_1.6-4_all.deb

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

iD8DBQFEkzcZ7ftwBTcVV3gRAvWkAJ47vJdDllIfQejI/q95UTxrUOG7pgCeJaVv
OCjqYKk/YIalYfG7pFk70OY=
=XMJL
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to