tl;dr: different packages own /usr/lib/pythonX/site-packages/tests and
different files with the same name inside that directory.
Hi all,
I was going through a package review and realized the package under
review owns
/usr/lib/pythonX/site-packages/tests
and some files inside the directory.
since there were no subdirectories and there were no namespaces for the
file names inside the directory, I went further and realized that the
following packages are doing the same:
python3-custodia-0:0.1.0-3.fc24.noarch
python3-django-federated-login-0:1.0.0-9.fc24.noarch
python3-journal-brief-0:1.1.3-3.fc24.noarch
python3-oauth2-0:1.9.0-2.post1.fc24.noarch
python3-repoze-who-plugins-sa-0:1.0.1-10.20160106gite1a36c5.fc24.noarch
python-custodia-0:0.1.0-3.fc24.noarch
python-django-federated-login-0:1.0.0-9.fc24.noarch
python-libturpial-0:1.7.0-4.fc24.noarch
python-repoze-who-plugins-sa-0:1.0.1-10.20160106gite1a36c5.fc24.noarch
what's the problem with that? Well what if we would have a package named
python-tests? shouldn't it own that directory? Also, since there are no
namespaces inside that directory for each package owning files in there,
they could end up owning different files with the same name. Actually,
the following packages own /usr/lib/python3.5/site-packages/tests/__init__.py
python3-custodia-0:0.1.0-3.fc24.noarch
python3-django-federated-login-0:1.0.0-9.fc24.noarch
python3-oauth2-0:1.9.0-2.post1.fc24.noarch
python3-repoze-who-plugins-sa-0:1.0.1-10.20160106gite1a36c5.fc24.noarch
or /usr/lib/python2.7/site-packages/tests/__init__.py
python-custodia-0:0.1.0-3.fc24.noarch
python-django-federated-login-0:1.0.0-9.fc24.noarch
python-libturpial-0:1.7.0-4.fc24.noarch
python-repoze-who-plugins-sa-0:1.0.1-10.20160106gite1a36c5.fc24.noarch
Is that all really a problem or am I missing something in the guidelines?
--
Athos Ribeiro
http://www.ime.usp.br/~athoscr