Bug 221442 - [maintainer-update] security/py-fail2ban: Update to 0.10.0
Summary: [maintainer-update] security/py-fail2ban: Update to 0.10.0
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Wen Heping
Depends on:
Reported: 2017-08-12 13:05 UTC by theis
Modified: 2017-10-12 11:00 UTC (History)
3 users (show)

See Also:
theis: maintainer-feedback+

patch (1.81 KB, patch)
2017-08-12 13:05 UTC, theis
theis: maintainer-approval+
Details | Diff
2nd patch (2.11 KB, patch)
2017-08-14 20:15 UTC, theis
theis: maintainer-approval+
Details | Diff
3rd Patch (3.62 KB, text/plain)
2017-08-18 08:59 UTC, theis
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description theis 2017-08-12 13:05:40 UTC
Created attachment 185319 [details]

Upgrade to latest version 0.10.0
Comment 1 theis 2017-08-14 20:15:06 UTC
Created attachment 185416 [details]
2nd patch

There was one bug that prevented the service to start: fali2bancmdline.py still expected the configuration under /etc instead ${ETCDIR}
Comment 2 theis 2017-08-18 08:59:17 UTC
Created attachment 185544 [details]
3rd Patch

I had to cherry-pick 2 more commits from upstream:

1) When using pf as the firewall starting fail2ban would delete all rules and not only the ones belonging to fail2ban

2) Some versions of python throw a lot of errors when trying to resolve an IP address
Comment 3 Dani 2017-10-12 06:13:36 UTC
Is there a reason why this wasn't commited yet? Would be cool to see this in the ports soon :-)
Comment 4 commit-hook freebsd_committer 2017-10-12 10:59:01 UTC
A commit references this bug:

Author: wen
Date: Thu Oct 12 10:58:43 UTC 2017
New revision: 451846
URL: https://svnweb.freebsd.org/changeset/ports/451846

  - Update t0 0.10
  - Update pkg-message

  PR:		221442
  Submitted by:	theis@gmx.at(maintainer)

Comment 5 Wen Heping freebsd_committer 2017-10-12 11:00:04 UTC
(In reply to Dani from comment #3)
Sorry for the delay.