In line with the Mass Python 2 Package Removal , the following (sub)packages of dnfdaemon 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 .
Trivial removal results in:
BUILDSTDERR: error: Installed (but unpackaged) file(s) found:
RPM build errors:
BUILDSTDERR: Installed (but unpackaged) file(s) found:
Maybe bad prefix? Any idea what's wrong?
The Makefile doesn't yet know how to not install Python 2 bindings. I haven't been able to get around to it, but if you want to propose a patch upstream for disabling the Python 2 bindings, I'd be happy to take that upstream and pull it in.
So the /lib/python/site-packages is just some default guess when it couldn't ask python2 where to put those files? In that case we can just delete them after %install and call it a temporary workaround.
Pretty much, yes.