Your message dated Thu, 17 May 2007 02:32:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#422655: fixed in fail2ban 0.8.0-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: fail2ban
Version: 0.8.0-1
Severity: serious
Tags: patch
Justification: violates Debian policy and the new Debian python module policy
Heya,
sorry to bother you again, but fail2ban leaves the *.pyc files in
/usr/share/fail2ban and it does not comply the new python policy. I've
prepared a patch which fixes that and a few other minor things I've seen
while preparing the patch, I'll send it as reply within a few minutes.
Please note that I've changed the packaging from python-central to
python-support, mainly because it's way more easy to handle imho, and it
doesn't have as many nasty bugs as python-central has. This is not a big
problem, as python-central didn't do anything in your packaging before.
Cheers,
Bernd
[...]
Unpacking fail2ban (from .../fail2ban_0.8.0-1_all.deb) ...
Setting up fail2ban (0.8.0-1) ...
Starting authentication failure monitor: fail2ban.
hal:~# dpkg -P fail2ban
(Reading database ... 257214 files and directories currently installed.)
Removing fail2ban ...
Stopping authentication failure monitor: fail2ban.
Purging configuration files for fail2ban ...
dpkg - warning: while removing fail2ban, directory
`/usr/share/fail2ban/server' not empty so not removed.
dpkg - warning: while removing fail2ban, directory
`/usr/share/fail2ban/client' not empty so not removed.
dpkg - warning: while removing fail2ban, directory
`/usr/share/fail2ban/common' not empty so not removed.
dpkg - warning: while removing fail2ban, directory `/usr/share/fail2ban'
not empty so not removed.
hal:~# find /usr/share/fail2ban
/usr/share/fail2ban
/usr/share/fail2ban/common
/usr/share/fail2ban/common/__init__.pyc
/usr/share/fail2ban/common/version.pyc
/usr/share/fail2ban/common/protocol.pyc
/usr/share/fail2ban/client
/usr/share/fail2ban/client/__init__.pyc
/usr/share/fail2ban/client/csocket.pyc
/usr/share/fail2ban/client/configurator.pyc
/usr/share/fail2ban/client/configreader.pyc
/usr/share/fail2ban/client/fail2banreader.pyc
/usr/share/fail2ban/client/jailsreader.pyc
/usr/share/fail2ban/client/jailreader.pyc
/usr/share/fail2ban/client/filterreader.pyc
/usr/share/fail2ban/client/actionreader.pyc
/usr/share/fail2ban/client/beautifier.pyc
/usr/share/fail2ban/server
/usr/share/fail2ban/server/__init__.pyc
/usr/share/fail2ban/server/jails.pyc
/usr/share/fail2ban/server/jail.pyc
/usr/share/fail2ban/server/actions.pyc
/usr/share/fail2ban/server/banmanager.pyc
/usr/share/fail2ban/server/banticket.pyc
/usr/share/fail2ban/server/ticket.pyc
/usr/share/fail2ban/server/mytime.pyc
/usr/share/fail2ban/server/jailthread.pyc
/usr/share/fail2ban/server/action.pyc
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 0.8.0-2
We believe that the bug you reported is fixed in the latest version of
fail2ban, which is due to be installed in the Debian FTP archive:
fail2ban_0.8.0-2.diff.gz
to pool/main/f/fail2ban/fail2ban_0.8.0-2.diff.gz
fail2ban_0.8.0-2.dsc
to pool/main/f/fail2ban/fail2ban_0.8.0-2.dsc
fail2ban_0.8.0-2_all.deb
to pool/main/f/fail2ban/fail2ban_0.8.0-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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yaroslav Halchenko <[EMAIL PROTECTED]> (supplier of updated fail2ban 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, 16 May 2007 14:13:57 -0400
Source: fail2ban
Binary: fail2ban
Architecture: source all
Version: 0.8.0-2
Distribution: unstable
Urgency: low
Maintainer: Yaroslav Halchenko <[EMAIL PROTECTED]>
Changed-By: Yaroslav Halchenko <[EMAIL PROTECTED]>
Description:
fail2ban - bans IPs that cause multiple authentication errors
Closes: 422655
Changes:
fail2ban (0.8.0-2) unstable; urgency=low
.
* Manually changing the order of debhelper inserted scripts in prerm
(Closes: #422655)
* Removed obsolete hack to have /bin/env invocation of python for
fail2ban-* scripts
* Applied changes submitted by Bernd Zeimetz (thanks Bernd):
- Removed obsolete Build-Depends-Indep on help2man, python-dev
- Explicit removal of *.pyc files compiled during build
- Invoke 'python setup.py clean' in clean target, which required also
to move python into Build-Depends
* Minor clean up of debian/rules
Files:
7000df20f2aadf3e9172a51c4f884156 672 net optional fail2ban_0.8.0-2.dsc
5ed8d97f8a1e8333f373d91f6fbbf83b 20753 net optional fail2ban_0.8.0-2.diff.gz
72d50735b5744e69a43191d4617c408a 73806 net optional fail2ban_0.8.0-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGS7uhjRFFY3XAJMgRAiHMAJ4opMvRgOsY9mHW4JjbnZzTckYDoQCfRwK9
GIbNSebfSZ3nAg7Vxw4XE3Q=
=aKoG
-----END PGP SIGNATURE-----
--- End Message ---
