(In reply to Andreas Stieger from comment #21) > Johannes, if this is too invasive, especially for working setups, we can > push this to 42.2. If you think this should be a 42.1 maintenance update > we'll review python-systemd. Andreas, when the sysadmins followed the fail2ban guidelines, then the update is not problematic (IMHO). Internally many things have changed. I have fail2ban currently running on at ~6 machines; all rules provided by fail2ban were running without issues but I had to adapt some of my additional rules. That's why I was waiting so long before submitting the update. There also was e.g. issue #971941 - such things may happen with the release and improper configured software.