Your message dated Mon, 04 Sep 2006 07:17:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380796: fixed in forg 0.5.1-7
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: forg
Version: 0.5.1-6
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: forg
Source-Version: 0.5.1-7
We believe that the bug you reported is fixed in the latest version of
forg, which is due to be installed in the Debian FTP archive:
forg_0.5.1-7.diff.gz
to pool/main/f/forg/forg_0.5.1-7.diff.gz
forg_0.5.1-7.dsc
to pool/main/f/forg/forg_0.5.1-7.dsc
forg_0.5.1-7_all.deb
to pool/main/f/forg/forg_0.5.1-7_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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
John Goerzen <[EMAIL PROTECTED]> (supplier of updated forg 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, 4 Sep 2006 08:56:10 -0500
Source: forg
Binary: forg
Architecture: source all
Version: 0.5.1-7
Distribution: unstable
Urgency: low
Maintainer: John Goerzen <[EMAIL PROTECTED]>
Changed-By: John Goerzen <[EMAIL PROTECTED]>
Description:
forg - Graphical Gopher Browser
Closes: 380796
Changes:
forg (0.5.1-7) unstable; urgency=low
.
* Update for new python policy. Closes: #380796.
* Update standards version.
Files:
de17145eb56a81ff2db312f5f8b29a6b 607 net optional forg_0.5.1-7.dsc
037253d83a8689bc3b237ca77ea1edc6 4938 net optional forg_0.5.1-7.diff.gz
a1dfd3ad02a4ca9aa7c5925e723c1626 75684 net optional forg_0.5.1-7_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE/DKh3PeFtIodmh8RAuT2AJ9dweoOQQSnGbixjpVp9kPhazUXeACfRsPI
IBIipZkD+HNemF7lDPt3Lqc=
=8Tcf
-----END PGP SIGNATURE-----
--- End Message ---
