Skip to content
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

extra-index-url is not taken into account if package exists in the index-url #2011

Closed
atti92 opened this issue Feb 27, 2024 · 1 comment
Closed
Labels
duplicate This issue or pull request already exists

Comments

@atti92
Copy link

atti92 commented Feb 27, 2024

If you have a package in a private repository and you add it as an extra-index-url, the resolver will throw conflict errors

uv pip compile requirements.txt
  × No solution found when resolving dependencies:
  ╰─▶ Because only the following versions of mypkg are available:
          mypkg<1.0.0rc6
          mypkg>=1.1.dev0
      and you require mypkg>=1.0.0rc6,<1.1.dev0, we can conclude that the requirements are unsatisfiable.

In my case pypi had 1 yanked version (0.0.0a1) and all valid versions are in the private repo.

This behaviour is contrary to pip because it can still find requirements in the extra-index-url.

workaround that works:

  • set pypi as extra-index-url
  • set private repo as index-url

  • The command you invoked: uv pip compile requirements.txt
  • The current uv platform: Ubuntu 22.04.1
  • The current uv version: 0.1.11
@charliermarsh
Copy link
Member

Thanks! This is the same as #1377.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants