[Python-modules-team] Bug#975565: fail2ban: Aborts due to Python 3.9 API change to Thread.isAlive()

[Michael Welsh Duggan]

Package: fail2ban
Version: 0.11.1-2
Severity: grave
X-Debbugs-Cc: none, Michael Welsh Duggan <md5i at md5i.com>

Dear Maintainer,

fail2ban fails to start, throwing the following error:

2020-11-22 22:12:13,384 fail2ban                [922]: ERROR   NOK: ("'FilterPyinotify' object has no attribute 'isAlive'",)

This is due to a Python API change in 3.9, changing
threading.Thread.isAlive() to thread.Thread.is_alive().  This seems to
be addressed in the upstream fail2ban sources by this pull request:

https://github.com/fail2ban/fail2ban/pull/2651


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fail2ban depends on:
ii  lsb-base  11.1.0
ii  python3   3.9.0-3

Versions of packages fail2ban recommends:
ii  iptables           1.8.6-1
ii  nftables           0.9.7-1
ii  python3-pyinotify  0.9.6-1.3
ii  python3-systemd    234-3+b3
ii  whois              5.5.7

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]            8.1.2-0.20180807cvs-2
ii  mailutils [mailx]            1:3.10-3+b1
pn  monit                        <none>
ii  rsyslog [system-log-daemon]  8.2010.0-1
ii  sqlite3                      3.33.0-1

-- no debconf information

-- 
Michael Welsh Duggan
(md5i at md5i.com)