Your message dated Mon, 14 Aug 2006 05:17:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380764: fixed in cx-bsdiff 1.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: cx-bsdiff
Version: 1.1-1
Severity: important
Hi, your package has been detected as generating a (for most of that
mass bug fill: private) 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 (which should
happend on tomorrow - Wed 2nd of July). 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
especially "Notes for packages with private modules/extensions"
Special Notes
* embedded interpreters: You don't *need* to do anything for your
package, though using XS/XB-Python-Version is much appreciated as it
helps tracking your package for binNMUs when python2.4 will become
default.
* if you need help updating your package, you can either:
- mail [email protected] ,
- tag your bug + help ,
- come on #debian-python/OFTC.
--- End Message ---
--- Begin Message ---
Source: cx-bsdiff
Source-Version: 1.1-2
We believe that the bug you reported is fixed in the latest version of
cx-bsdiff, which is due to be installed in the Debian FTP archive:
cx-bsdiff_1.1-2.diff.gz
to pool/main/c/cx-bsdiff/cx-bsdiff_1.1-2.diff.gz
cx-bsdiff_1.1-2.dsc
to pool/main/c/cx-bsdiff/cx-bsdiff_1.1-2.dsc
python-bsdiff_1.1-2_i386.deb
to pool/main/c/cx-bsdiff/python-bsdiff_1.1-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.
Daniel Baumann <[EMAIL PROTECTED]> (supplier of updated cx-bsdiff 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: Mon, 14 Aug 2006 13:44:00 +0200
Source: cx-bsdiff
Binary: python-bsdiff
Architecture: source i386
Version: 1.1-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann <[EMAIL PROTECTED]>
Changed-By: Daniel Baumann <[EMAIL PROTECTED]>
Description:
python-bsdiff - generate/apply a patch between two binary files (python module)
Closes: 380764
Changes:
cx-bsdiff (1.1-2) unstable; urgency=low
.
* New email address.
* Very appreciating NMU (Closes: #380764).
* Minor formal changes.
Files:
d1e13d9fd67c8ab8f3ca9762b82a2944 606 python optional cx-bsdiff_1.1-2.dsc
d1dbdbf803155ddc7c41599d3a7e1446 4289 python optional cx-bsdiff_1.1-2.diff.gz
ba6e0b8cda0eb1b0f2bc6dc39f363b94 22282 python optional
python-bsdiff_1.1-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE4Gc3+C5cwEsrK54RAkMAAJsEBoyeR+Fd/gl78fkOQq9Fv3scswCgyzdb
ydbItkdj/+UwNUuaPVhqHeM=
=yGxz
-----END PGP SIGNATURE-----
--- End Message ---
