Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fail2ban should be UPDATED #109

Open
cicku opened this issue Jan 30, 2012 · 5 comments
Open

fail2ban should be UPDATED #109

cicku opened this issue Jan 30, 2012 · 5 comments
Labels

Comments

@cicku
Copy link

cicku commented Jan 30, 2012

New version just come out!!!Should be UPDATED

@dagwieers
Copy link
Member

No drama needed !!!!

The latest release (0.8.6) is not available from Github or Sourceforge. Also the new Github downloads are not compatible with how SPEC files and RPM packages work. We need actualy .tar.gz downloads, not URLs that do not contain the actual filename :-/

@dagwieers
Copy link
Member

TIP: You're welcome to update the packages yourself through Github and do a pull-request, that's by far the fastest way to get something implemented.

@cicku
Copy link
Author

cicku commented Jan 30, 2012 via email

@cicku
Copy link
Author

cicku commented Jan 30, 2012

OK

@cicku cicku closed this as completed Jan 30, 2012
@dagwieers dagwieers reopened this Jan 30, 2012
@dfateyev
Copy link
Member

I've tried with the latest 0.8.7.1 version and it has been built fine with the existing spec. But here's the thing: there are a bunch of patches for new versions in RH and Debian lists (you may see some applied in EPEL package.) Sure, I can play with the package and patch set, but it will take some time and, since I haven't used "fail2ban" for a while it can produce unusable results..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants