On Wed, 06 Jul 2022 at 21:08:28 +0200, Enrico Zini wrote: > On Wed, Jul 06, 2022 at 05:10:54PM +0200, Bastian Germann wrote: > > Why is it defunct? Is it also in Debian? If not this is not a serious > > bug. > > https://github.com/seb-m/pyinotify "pyinotify" which is upstream for > python3-pyinotify in Debian, is dead since 2015.
There seems to be a newer fork of this codebase at <https://github.com/lexdene/pyinotify> and <https://pypi.org/project/pyinotify-elephant-fork/> (I have not reviewed it, it might be broken or even malicious). If this fork is maintained and high-quality, then one option would be to switch the upstream of Debian's python3-pyinotify package to this fork. The fork removed the asyncore integration completely <https://github.com/lexdene/pyinotify/commit/dbc19878b3b3e50d9a065c3d5290002eb9b61372>, which is an API break that addresses #1040102 but would break at least ganeti. The maintainer of the fork does not seem to have made any attempt to address other bugs, so it seems too early to say whether there is going to be ongoing maintenance. > https://github.com/dsoprea/PyInotify "inotify" is not packaged in > Debian. This is now <https://tracker.debian.org/pkg/python-inotify>. For packages where a dependency on GLib is acceptable, using python3-gi's Gio.FileMonitor is another alternative (for example autokey, cinnamon and mate-hud should probably use that, since their GUI toolkits require GLib anyway). > It remains that this package > should likely not be used except by obsolete code that we probably > shouldn't have in Debian. The transition to Python 3.12 makes this more urgent, due to #1075939. I've opened bugs in all reverse-dependencies, and set them to "block" this bug. smcv
