Description of problem: Upstream has significant new features that make current version outdated.
Version-Release number of selected component (if applicable): 0.8.11-2
How reproducible: N.A.
Steps to Reproduce: N.A.
Actual results: Less features, still some open bugs
Expected results: More features, some bugs fixed
Created attachment 895965 [details]
Modified spec file
Created attachment 895966 [details]
Patch for file badips.py
Builds with Fedora 21 source rpm and these modifications:
Modified .spec file
updated release 5->1
removed tests execution
It will add dependencies libmnl and ipset.
Fedora 21 source RPM:
Sorry for multiple posts (no idea how to attach multiple files to a new comment).
Created attachment 896376 [details]
New spec file
Some configuration files (e.g. action.d dir) were excluded from build. Now they are included.
I used your spec file and made some edits for RH6 builds with regards to systemd, firewalld and tmpfiles.d
Added a small patch for the recidive plugin and added logfile creation for /var/log/fail2ban.log.
Created attachment 902475 [details]
Spec file with rhel6 changes
Created attachment 902476 [details]
added ignoreregex line to recidive filter
I'm very hesitant to do this due to the large number of changes to the configuration files.
*** Bug 1190909 has been marked as a duplicate of this bug. ***
Any update on this one? Managing f2b on EL6 and EL7 is completely different now.
Could anyone tell me whats the problem atm? I used the spec file from the EL7 release and added some minor if/else changes based on OS version (eg. skipping systemd and firewalld).
It builds without problems and seems to work.
Or is the main pain with the 0.9 release that configuration changes are quiet big and do not find in a LTS version?
Epel 6 still has 0.8.14 only. I don't know why it can't be updated to 0.9.1. Only Orion can answer your question. If your spec file builds ok on epel 6 too, and the only concern is stability, admins could be given the choice to install either 0.8.14 or 0.9.1.
Please give the package from https://copr.fedoraproject.org/coprs/orion/fail2ban-el6/ a try. If everyone reports smooth upgrades with no surprises, I'll update the EPEL6 package to it.
For what it's worth, so far so good.
I have done clean installs, updates to hosts with simple configs and updates to one host with a less than simple config.
No issues thus far!
fail2ban-0.9.2-1.el6 has been submitted as an update for Fedora EPEL 6.
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing fail2ban-0.9.2-1.el6'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
fail2ban-0.9.2-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
root@sl6 ~ # yum update
Loaded plugins: downloadonly, security
Setting up Update Process
--> Running transaction check
---> Package fail2ban.noarch 0:0.8.14-2.el6 will be updated
---> Package fail2ban.noarch 0:0.9.2-1.el6 will be an update
--> Processing Dependency: ipset for package: fail2ban-0.9.2-1.el6.noarch
--> Finished Dependency Resolution
Error: Package: fail2ban-0.9.2-1.el6.noarch (epel)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
root@sl6 ~ # uname -r
Works for me:
Package Arch Version Repository Size
fail2ban noarch 0.9.2-1.el6 epel 410 k
Installing for dependencies:
gamin-python x86_64 0.1.10-9.el6 rhel-6-server-rpms 33 k
ipset x86_64 6.11-4.el6 rhel-6-server-rpms 63 k
libmnl x86_64 1.0.2-3.el6 rhel-6-server-rpms 21 k
python-inotify noarch 0.9.1-1.el6 epel 50 k
doh! my bad, this box runs SL6, not RHEL6.
Sorry for the noise.
Should work fine on SL6 too:
ipset.x86_64 6.11-3.el6 @sl