Closed geerlingguy closed 3 years ago
Yuck. It looks like that version of distribute
is from 2012! https://pypi.org/project/distribute/0.6.27/
Hmm...
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. If you want to abort this run, you can press Ctrl + C to do so.
It keeps resolving back to older and older and older coverage
packages until it hits 3.5.3
and explodes.
With the above PR, I'm getting:
The conflict is caused by:
The user requested kubernetes==12.0.0
openshift 0.11.2 depends on kubernetes~=11.0.0
The user requested kubernetes==12.0.0
openshift 0.11.1 depends on kubernetes~=11.0.0
The user requested kubernetes==12.0.0
openshift 0.11.0 depends on kubernetes~=11.0
The user requested kubernetes==12.0.0
openshift 0.10.3 depends on kubernetes~=10.0
The user requested kubernetes==12.0.0
openshift 0.10.2 depends on kubernetes~=10.0.1
The user requested kubernetes==12.0.0
openshift 0.10.1 depends on kubernetes~=10.0.1
The user requested kubernetes==12.0.0
openshift 0.10.0 depends on kubernetes~=10.0
The user requested kubernetes==12.0.0
openshift 0.9.3 depends on kubernetes~=9.0.0
The user requested kubernetes==12.0.0
openshift 0.9.2 depends on kubernetes~=9.0.0
To fix this you could try to:
1. loosen the range of package versions you've specified
It looks like the error is happening in the downstream tests as a result of https://github.com/ansible-collections/community.kubernetes/pull/276 from @jaydesl — @Akasurde do you know of any quick fix? It seems like it could be we need the openshift library to update its own dependencies?
@geerlingguy This is due to new pip dependency resolver. We can't install
kubernetes==12.0.0
openshift>=0.9.2
coverage
with this combination we get -
Cannot install kubernetes==12.0.0, openshift==0.10.0, openshift==0.10.1, openshift==0.10.2, openshift==0.10.3, openshift==0.11.0, openshift==0.11.1, openshift==0.11.2, openshift==0.9.2 and openshift==0.9.3 because these package versions have conflicting dependencies.
trying option --use-deprecated=legacy-resolver
from https://blog.python.org/2020/11/pip-20-3-release-new-resolver.html
@Akasurde - But is there any way to get a resolvable set of dependencies? It seems like that would be a good goal, regardless of how strict Pip wants to be about it.
SUMMARY
On the task:
There is currently a failure when running
pip3 install kubernetes==12.0.0 openshift>=0.9.2 coverage
:ISSUE TYPE
COMPONENT NAME
CI tests.