The /usr/lib64/python3.7/site-packages/ directory is supposed to be owned by python3-libs, not this package. Please fix the %files section not to include: %{python3_sitearch} - /usr/lib64/python3.7/site-packages/ When you do it, please make sure not to own /usr/lib64/python3.7/site-packages/__pycache__ either.
I am surprised that this occurs. In the spec file we have: %global srcname natsort ... %files -n python3-%{srcname} %license LICENSE %doc README.rst %{_bindir}/%{srcname} %{python3_sitelib}/%{srcname}-*.egg-info/ %{python3_sitelib}/%{srcname}/ In no place the spec includes sitearch, only sitelib...
$ dnf repoquery --repo=rawhide -f /usr/lib64/python3.7/site-packages python3-cheetah-0:3.1.0-7.fc30.x86_64 python3-libs-0:3.7.2-6.fc30.x86_64 python3-pystatgrab-0:0.7-13.fc30.x86_64 python3-rpy-0:2.9.5-2.fc30.x86_64 We are talking rpy, not natsort. Rpy actually has sitearch: %files -n python3-%{srcname} %doc AUTHORS NEWS PKG-INFO %{python3_sitearch}/%{srcname}* However, I've fixed the problem while fixing another problem: https://src.fedoraproject.org/rpms/rpy/c/6ff7586c762c83a0831992847f6c85042b3d4ce0?branch=master Yet in order to truly fix this a build needs to be made. Since this issue is not very severe, it can wait for the next "natural" build - an update or F31 mass rebuild.
OK. You are right. :-) I have two python packages with updates avaialable, rpy (3.0.0) and python-natsort (6.0.0). So it is natural to see what could be improved with the update, except when you mix the report for one package with the other. :-) Build rpy-3.0.0-1.fc31 (also available for F30) fixes the issue. Thanks for the report.