Cannot install specific version of private repo #10257
Replies: 1 comment
-
|
I could make it work for another project. So I believe the issue is related to the keychain. It seems that the computer is caching the wrong key for the latest packages, but I'm not sure how to fix that. This is not related to poetry, though. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello there!
I'm facing a weird issue with poetry, and I wonder if someone could help me out. I'm using Poetry 1.8.3 on a mac, and I created a private repo in GCP.
The package was simple, and just contained a function to add two numbers. I followed mostly what was here, and I could publish the private repo in GCP without any issues.
When installing the package in a new repo, for testing, things were working like a charm, and this is the
pyproject.tomlI have on the new repo (regions, project names, python repos, etc were masked with random names below):With the package above, I also setup the system to access the private repository using oauth2, like below:
This works great, for versions 0.1, 0.2, 0.3, and 0.4, but from 0.5 onwards it starts to fail, giving a 401 error:
HTTPError 401 Client Error: Unauthorized for url: ....And any package that I try to create now cannot be installed, but can be published.
I'm a little stuck, and any help would be appreciated. I tried to find for similar issues, like this one, but I still couldn't fix this.
Beta Was this translation helpful? Give feedback.
All reactions