Your message dated Fri, 8 Sep 2006 12:57:55 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in NMU of entity 1.0.1-7.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: entity
Version: 1.0.1-7.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 ---
Version: 1.0.1-7.2
I've NMUed for this bug (fixing the bug to use versioning instead of the
"fixed" tag, to ease tracking through testing); here's the changelog:
> entity (1.0.1-7.2) unstable; urgency=low
> .
> * Non-maintainer upload.
> * Update Build-depends to the new Python policy; change build-dependency on
> python2.3-dev to one on python-dev, and remove the demand that python
> should be (<< 2.4). Fixes FTBFS. (Closes: #380787, 383989)
/* Steinar */
--
Homepage: http://www.sesse.net/
--- End Message ---
