Bug#380902: marked as done (Python transition (#2): you are building a private python module !)
Your message dated Tue, 01 Aug 2006 15:36:53 -0700
with message-id <E1G82r7-00073V-Kw@spohr.debian.org>
and subject line Bug#380902: fixed in pyching 1.2.2-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: pyching
Version: 1.2.2-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: pyching
Source-Version: 1.2.2-2
We believe that the bug you reported is fixed in the latest version of
pyching, which is due to be installed in the Debian FTP archive:
pyching_1.2.2-2.diff.gz
to pool/main/p/pyching/pyching_1.2.2-2.diff.gz
pyching_1.2.2-2.dsc
to pool/main/p/pyching/pyching_1.2.2-2.dsc
pyching_1.2.2-2_all.deb
to pool/main/p/pyching/pyching_1.2.2-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 380902@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matej Vela <vela@debian.org> (supplier of updated pyching 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 22:58:30 +0200
Source: pyching
Binary: pyching
Architecture: source all
Version: 1.2.2-2
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Matej Vela <vela@debian.org>
Description:
pyching - A Python program to cast and interpret I Ching hexagrams
Closes: 380902
Changes:
pyching (1.2.2-2) unstable; urgency=low
.
* QA upload.
* Switch to new Python policy. Closes: #380902.
* Switch to debhelper 5.
* pyching.pyw: Useful only on Windows; remove.
* debian/pyching: Use pyching.sh instead.
* debian/pyching.1: Now integrated upstream.
* debian/rules: Use binary-indep rather than binary-arch.
* debian/watch: Add.
* Conforms to Standards version 3.7.2.
Files:
8cc644b8e8cd44861282aab7382663a4 648 games optional pyching_1.2.2-2.dsc
2a4718db7eae882a0615ee06c7ba3106 3710 games optional pyching_1.2.2-2.diff.gz
02494c8adea397e0e35c3610dc2063e8 130740 games optional pyching_1.2.2-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEz8CnxBYivKllgY8RAkgeAJ9zgYo0HtfJ/+ZKjIJzvWM4vAOo3QCeLPcE
7ZnrwlzrxCrVd2KMFmnvwkQ=
=Kz/r
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: