-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package conflicts when installing client bindings #363
Comments
I wonder if this is also a problem in upstream. It's odd to me that they chose the |
Did some further investigation in a python container:
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 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 |
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
The text was updated successfully, but these errors were encountered: