Your message dated Sat, 23 Dec 2006 21:12:36 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380995: Python transition (#2): you are building a private
python module !
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: zpkg
Version: 1.0.0-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 ---
zpkg has been removed from unstable, so I am closing this bug.
On Tue, Aug 01, 2006 at 12:32:53PM +0200, [EMAIL PROTECTED] wrote:
> Package: zpkg
> Version: 1.0.0-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.
>
>
>
--
Brian Sutherland
Metropolis - "it's the first movie with a robot. And she's a woman.
And she's EVIL!!"
--- End Message ---
