Your message dated Tue, 29 Aug 2006 17:17:38 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380788: fixed in epylog 1.0.3-5
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: epylog
Version: 1.0.3-4
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: epylog
Source-Version: 1.0.3-5
We believe that the bug you reported is fixed in the latest version of
epylog, which is due to be installed in the Debian FTP archive:
epylog_1.0.3-5.dsc
to pool/main/e/epylog/epylog_1.0.3-5.dsc
epylog_1.0.3-5.tar.gz
to pool/main/e/epylog/epylog_1.0.3-5.tar.gz
epylog_1.0.3-5_all.deb
to pool/main/e/epylog/epylog_1.0.3-5_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.
Julien Louis <[EMAIL PROTECTED]> (supplier of updated epylog 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: Wed, 30 Aug 2006 00:59:39 +0200
Source: epylog
Binary: epylog
Architecture: source all
Version: 1.0.3-5
Distribution: unstable
Urgency: low
Maintainer: Tiago Bortoletto Vaz <[EMAIL PROTECTED]>
Changed-By: Julien Louis <[EMAIL PROTECTED]>
Description:
epylog - New logs analyzer and parser
Closes: 379927 380788 385203
Changes:
epylog (1.0.3-5) unstable; urgency=low
.
[ Tiago Bortoletto Vaz ]
* A lot of changes to be in conformity with the new python policy.
(Closes: #380788)
.
[ Julien Louis ]
* debian/control:
+ Remove perl-doc from Build-Depends.
* Add patch 02_fix_perl_man_generation to build epylog.3 correctly
(Closes: #379927).
* debian/rules:
+ Remove unneeded configure call in build target.
* Don't hardcode path of *.pyc modules (Closes: #385203).
Files:
69f9a7858417a1d14b6d69f3443e418f 689 python extra epylog_1.0.3-5.dsc
537eb199897786ad15c17215cf99f8d4 143083 python extra epylog_1.0.3-5.tar.gz
860cce42c78b4fd2f9af905832de22ed 85786 python extra epylog_1.0.3-5_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE9NU4LqiZQEml+FURApNSAJ4pxF2Kbypwx0qUd/QYAKqLa8nOKQCgqoIr
CBgnI8Zpy7KF0jYI/6cpaOY=
=ctmI
-----END PGP SIGNATURE-----
--- End Message ---