-
Notifications
You must be signed in to change notification settings - Fork 25
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
Cannot download some package #23
Comments
Hi,
Whether an older one is downloaded successfully:
On the server side i have these logs:
I am still digging on my side |
I am still debugging on the pip side (client) to understand how it works: I modified this file locally in
My line is here: Now i am able to download my package successfully:
It seems that some packages are saying that they should expose a kind of metadata file (a kind of description file) but proxpi is not mirroring it. I followed the function here _internal/models/link.py (always in pip client side):
So indeed, some packages seems now to support pep658 (https://peps.python.org/pep-0658/#specification) in their build process. This is confirmed by my command: We can see these lines:
So the format has changed in the last release to respect pep658 I will now try to workaround that by in proxpi. As i am not a proxpi developer, my idea is to simply mirror the same package name (expanded with .metadata) if it it exists in the original repository. I will let you know |
I changed my mind, because i have found a better/faster workaround, and as i my blocked, i need to go faster. As I understood how proxpi is creating the index for each package, i was able to skip and This is my patch:
If you are using the docker image, do not forget to restart the container to see the change reflected by Gunicorn Now the same curl give the suitable output: output:
I reverted my pip client as it was, and now I am able to download my package:
I still believe that the good solution is to mirror the metadata file, but for blocked people (like me in production) this is the fastest way I found to make the change locally in proxpi. @ZuluPro you have here a workaround if you are blocked Thanks to proxpi and to the project maintainer. |
Hi @hzrari Do you plan to do a PR ? |
Hello @ZuluPro It is included in this version: https://github.com/EpicWink/proxpi/releases/tag/v1.1.0rc0 As we can see on the hub, it is not tagged as |
Caused by pypi/warehouse#13649
|
ok @EpicWink , Indeed, I have seen indeed the huge work and thank you for that. Regards |
As it is fixed in version 1.1.0rc0 : https://github.com/EpicWink/proxpi/releases/tag/v1.1.0rc0 I close this issue. Thank you guys |
Note, you Solve by doing one of:
|
v1.1 has now been released |
With a brand-new docker install, I cannot download some package.
The latest version raise a 404 for .metadata
Reproduction
Here's some example with Sphinx==7.0.1:
With the original repo it works:
Also previous versions of Sphinx works:
Expected behaviour
I should be able to install the last package transparently
Actual behaviour
Include current behaviour and output.
Environment
proxpi
: latestThe text was updated successfully, but these errors were encountered: