In line with the Mass Python 2 Package Removal , the following (sub)packages of avahi were marked for removal:
According to our query, those (sub)packages only provide a Python 2 importable module. If this is not true, please tell us why, so we can fix our query.
Please remove them from your package.
As said in the change document, if there is no objection in a week, we will remove the package(s) as soon as we get to it. This change might not match your packaging style, so we'd prefer if you did the change. If you need more time, please let us know here.
We hope this doesn't come to you as a surprise. If you want to know our motivation for this, please read the change document .
portions of avahi-ui-tools (also a subpackage of avahi),
depend on python2-avahi, so those portions would need to be removed as well.
This is a flow in our automation.
When it searches leave packages, it tends to ignore dependent packages from the same SRPM.
Can we move this to Python 3?
I can look again, but last I did it was not compatible with python3 (I don't remember why though)
Confirmed, avahi-discover at least depends on pygtk2 which has no python3 equivalent. So we can't get rid of python2-avahi (yet)