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

poetry update uses secondary repo for all dependencies listed in pyproject.toml #5538

Closed
3 tasks done
diegoquintanav opened this issue May 4, 2022 · 2 comments
Closed
3 tasks done
Labels
kind/bug Something isn't working as expected

Comments

@diegoquintanav
Copy link

  • I am on the latest Poetry version.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

Issue

  • I install my project inside a docker container
  • everything works fine: pipy dependencies are installed from pipy, my custom pipy dependency is installed from source
  • I access to the container shell
  • run poetry update
  • I get an error:
401 Client Error: Unauthorized for url: https://pypi.myrepo.org/simple/pytest/

Poetry is looking for pytest in myrepo although it did not did so when doing install. What am I doing wrong?

Note that the URL of pypi.myrepo.org is masked and I can't provide credentials for obvious reasons.

@diegoquintanav diegoquintanav added kind/bug Something isn't working as expected status/triage This issue needs to be triaged labels May 4, 2022
@diegoquintanav diegoquintanav changed the title poetry update uses secondary repo listed in pyproject.toml poetry update uses secondary repo for all dependencies listed in pyproject.toml May 4, 2022
@abn
Copy link
Member

abn commented May 4, 2022

This is a duplicate of #4704 for an explanation of what is happening see #4704 (comment).

@abn abn closed this as completed May 4, 2022
@mkniewallner mkniewallner removed the status/triage This issue needs to be triaged label Jun 11, 2022
Copy link

github-actions bot commented Mar 1, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Something isn't working as expected
Projects
None yet
Development

No branches or pull requests

3 participants