Description of problem: fail2ban still supports gamin. In shifting to python3 it would be nice to be able to keep gamin support.
Added blocker on meta-tracker bug 1285816, per current SOP.
Fail2ban+gamin+SELinux is broken, and probably unfixable: https://bugzilla.redhat.com/show_bug.cgi?id=437633 https://mail.gnome.org/archives/gamin-list/2008-May/msg00000.html As such, I'd honestly recommend ditching gamin support in fail2ban, rather than encouraging users to disable SELinux. Gamin wasn't really designed to support the use case of fail2ban, and since there are better suited backends for fail2ban, it seems and unecessary burden to support gamin (and hold back python3 adoption by fail2ban as a result).
This will need work, looks like upstream (gamin) doesn't support python3 out of the box
gamin seems largely dead upstream...
(In reply to Jonathan Underwood from comment #4) > gamin seems largely dead upstream... yep, I'd sooner kill it off entirely.
Just FYI, $ repoquery --whatrequires gamin caja-0:1.14.0-1.fc24.x86_64 codeblocks-contrib-0:13.12-23.fc24.x86_64 doodle-0:0.7.0-10.fc24.x86_64 glib2-fam-0:2.48.0-1.fc24.x86_64 gnome-vfs2-0:2.24.4-20.fc24.x86_64 kdelibs-6:4.14.18-3.fc24.x86_64 lighttpd-0:1.4.39-3.fc24.x86_64 ocaml-omake-0:0.9.8.6-0.rc1.fc24.22.x86_64 strigi-0:0.7.8-12.fc24.x86_64 thunar-vfs-0:1.2.0-17.fc24.x86_64
python support has been dropped completely. Amazingly, some things still require gamin: caja-1.22.2-1.fc32.src.rpm codeblocks-17.12-14.fc31.src.rpm glib2-2.63.0-1.fc32.src.rpm gnome-vfs2-2.24.4-29.fc31.src.rpm lighttpd-1.4.54-2.fc31.src.rpm thunar-vfs-1.2.0-25.fc31.src.rpm