Open maartenbeeckmans opened 2 years ago
I wonder if this is also a problem in upstream. It's odd to me that they chose the pulpcore.client
namespace. It implies the client tools need pulpcore
to be installed too, but that's not logical.
Did some further investigation in a python container:
1) when I only install pulpcore-client with pip it creates the following files:
root@88697ba93215:/usr/local/lib/python3.10/site-packages/pulpcore# pwd
/usr/local/lib/python3.10/site-packages/pulpcore
root@88697ba93215:/usr/local/lib/python3.10/site-packages/pulpcore# ls
__init__.py __pycache__ client
root@88697ba93215:/usr/local/lib/python3.10/site-packages/pulpcore/client# pwd
/usr/local/lib/python3.10/site-packages/pulpcore/client
root@88697ba93215:/usr/local/lib/python3.10/site-packages/pulpcore/client# ls
__init__.py __pycache__ pulpcore
Client bindings are under the pulpcore folder
2) when I only install pulp-rpm-client with pip it creates the following files
root@e84e84946736:/usr/local/lib/python3.10/site-packages/pulpcore# pwd
/usr/local/lib/python3.10/site-packages/pulpcore
root@e84e84946736:/usr/local/lib/python3.10/site-packages/pulpcore# ls
__init__.py __pycache__ client
root@e84e84946736:/usr/local/lib/python3.10/site-packages/pulpcore/client# pwd
/usr/local/lib/python3.10/site-packages/pulpcore/client
root@e84e84946736:/usr/local/lib/python3.10/site-packages/pulpcore/client# ls
__init__.py __pycache__ pulp_rpm
Client bindings are under the pulp_rpm folder
3) when I install both pulpcore-client and pulp-rpm-client with pip it creates the following files
root@0150e93eb1dd:/usr/local/lib/python3.10/site-packages/pulpcore# pwd
/usr/local/lib/python3.10/site-packages/pulpcore
root@0150e93eb1dd:/usr/local/lib/python3.10/site-packages/pulpcore# ls
__init__.py __pycache__ client
root@0150e93eb1dd:/usr/local/lib/python3.10/site-packages/pulpcore/client# pwd
/usr/local/lib/python3.10/site-packages/pulpcore/client
root@0150e93eb1dd:/usr/local/lib/python3.10/site-packages/pulpcore/client# ls
__init__.py __pycache__ pulp_rpm pulpcore
Client bindings are installed under the pulp_rpm and pulpcore folders
For testing I was using the python:bullseye container with python 3.10 installed, but that shouldn't really matter
So when installing it with pip, some files like the __init__.py
and __pycache__
folder and subfiles are managed by both pip packages. Pip doesn't really care about it but yum/dnf/rpm does.
No idea how we should proceed with this.
Looks indeed that they are installed in the same namespace.
I think this should be taken up with upstream. I know Python has a mechanism with .pth
files but I've never used it and don't know if it's really a solution.
When I'm installing client bindings for some custom scripting with packages from the rpm repository, there are package conflics as multiple files are owned by the same repository.
python3-pulpcore-client and python3-pulpcore have conflicts on the same file The same is happening for python3-pulpcore-client and python3-pulp-rpm-client
Already tried the option --best but that isn't helping.
Using a mirror (updated to upstream) of the pulpcore 3.14 repository Vm is running EL8