Comment 64 for bug 2055114
Revision history for this message
| Mauricio Faria de Oliveira (mfo) wrote | #64 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
The vendorized asyncore.py is identical in python3-pyasyncore (main).
It's better to rely on the package (vs. vendoring) for the stable release,
specially for an LTS, where ESM is 10-12 years, to avoid code duplication
and monitoring/patching on potential security vulnerabilities in 2 places.
Also, in the future, if upstream does migrate from asyncore to asyncio,
the compat module might be abandoned and we'd lose updates/fixes, if any;
and, if this were to happen, again, it's potential bug fixes in 2 places.
I discussed the approach with Steve L., and he confirmed this to be fine.
So, I adjusted the existing 2 uploads, build/start tested in PPA/locally,
and confirmed the asyncore module comes from python3-pyasyncore, and the
asynchat module comes from fail2ban compat/vendoring.
Re-uploading to Noble.
...
$ sudo apt install -y python3-pyasyncore
$ dpkg -S /usr/lib/
python3-pyasyncore: /usr/lib/
$ wget 'https:/
$ md5sum asyncore.py /usr/lib/
b4d0825373f6b54
b4d0825373f6b54
...
PPA build with -proposed enabled:
https:/
$ systemctl status --full --no-pager fail2ban.service
...
Active: active (running) since Mon 2024-06-10 19:33:55 -03; 7s ago
...
Jun 10 19:33:55 noble-fail2ban systemd[1]: Started fail2ban.service - Fail2Ban Service.
Jun 10 19:33:55 noble-fail2ban fail2ban-
Jun 10 19:33:55 noble-fail2ban fail2ban-
...
$ sudo systemctl stop fail2ban.service
$ sudo strace -e openat /usr/bin/python3 /usr/bin/
openat(AT_FDCWD, "/usr/lib/
openat(AT_FDCWD, "/usr/lib/