Bug#380803: marked as done (Python transition (#2): you are building a private python module !)
Your message dated Tue, 01 Aug 2006 15:34:03 -0700
with message-id <E1G82oN-0005iS-KK@spohr.debian.org>
and subject line Bug#380803: fixed in galternatives 0.13.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: galternatives
Version: 0.13.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 debian-python@lists.debian.org ,
- tag your bug + help ,
- come on #debian-python/OFTC.
--- End Message ---
--- Begin Message ---
Source: galternatives
Source-Version: 0.13.2
We believe that the bug you reported is fixed in the latest version of
galternatives, which is due to be installed in the Debian FTP archive:
galternatives_0.13.2.dsc
to pool/main/g/galternatives/galternatives_0.13.2.dsc
galternatives_0.13.2.tar.gz
to pool/main/g/galternatives/galternatives_0.13.2.tar.gz
galternatives_0.13.2_all.deb
to pool/main/g/galternatives/galternatives_0.13.2_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 380803@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pierre Habouzit <madcoder@debian.org> (supplier of updated galternatives 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 ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 1 Aug 2006 21:39:35 +0200
Source: galternatives
Binary: galternatives
Architecture: source all
Version: 0.13.2
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Pierre Habouzit <madcoder@debian.org>
Description:
galternatives - graphical setup tool for the alternatives system
Closes: 380803
Changes:
galternatives (0.13.2) unstable; urgency=low
.
* QA upload.
* Update package to the last python policy (Closes: #380803).
Files:
de158e194ea9efbf4ad70783d1a9d12a 608 admin optional galternatives_0.13.2.dsc
dd63e2af1b4269fe35c723a35aa39e95 28388 admin optional galternatives_0.13.2.tar.gz
3de6fae16155757aec09bb46086315c7 27966 admin optional galternatives_0.13.2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEz7ApvGr7W6HudhwRApY9AJ9PC2Z1xOjfM/3fP/qhiwXQE1t6lgCeNNDg
ExXcBAa1OUvl/zI1mrAHWOA=
=Gve+
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: