-
Notifications
You must be signed in to change notification settings - Fork 3k
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
--unstable-feature=resolver
fails to recognize dependencies between explicit dist URLs
#8433
Comments
The "easiest" case to reproduce this seems to be:
This seems to be an issue due to the interaction of @pfmoore Could you try this out with your PR for #8377, and see what that generates? I wonder if we would've generated a useful error message to hint that something was wrong in this case. |
I'm not 100% sure if this should block "stable" or beta, so I've put it in the "prod" pool. |
Does this work on master? This is why we did the resolvelib 0.4 rewrite, if I read it correctly. |
What is the procedure for testing against master? |
Just install pip from GitHub:
|
I'll try. Installing from the local Git repo exploded... Oh, it's not pip that explodes. It's Ansible's |
Hi @webknjaz - can I check, is the above comment confirming that there's not a pip issue here, but rather an issue with ansible? Or am I misunderstanding? |
Yeah, it looks like it, sorry for the noise. |
No worries, I appreciate you putting the time in to help test :-) |
I have a CI that pulls in
ansible
andansible-base
from theirrespective unreleased "devel" locations.
ansible
depends onansible-base
. Both have target versions2.10.0
I was using thefollowing form for pip's arguments (originally):
ansible @ https://github.com/ansible/ansible.git@devel
andansible-base @ https://toshio.fedorapeople.org/ansible/acd/ansible/ansible-2.10.0.tar.gz
.ansible
has a dependencyansible-base<2.11.0,>=2.10.0
.At some point, this started failing so I started experimenting on
how to fix it. Here's the forms I've tried:
And I've also enabled
--unstable-feature=resolver
which happens tohave the same issue. And the issue is that
pip install
says that itcannot fulfill these two deps (even though the log says that it has
downloaded both tarballs and recognized their deps).
Failure example: https://github.com/ansible/ansible-lint/runs/762485001#step:8:581
Here's a verbose log output: https://gist.github.com/webknjaz/4516cf3f6b6984f91501c1789826ff60
The most interesting part extracted:
The text was updated successfully, but these errors were encountered: