-
-
Notifications
You must be signed in to change notification settings - Fork 97
publish fails due to rust compiler not found #56
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
Comments
It looks like they upgraded the manylinux tag on their wheel, so would need to install an upgraded version of pip before installing twine. |
Yes, they've dropped manylinux1 as a pre-requisite for starting to use the Rust toolchain (pyca/cryptography#5410 (comment) / pyca/cryptography#5776). And yes, you may be onto something: if pip is too old, it wouldn't know about the manylinux2010/manylinux2014 tags. Good catch! Let me verify this locally. |
Actually, looking again, it seems like they did an incomplete push, there's only python 3.6 wheels present. |
Filed bug at pyca/cryptography#5787 |
Ah, you are right! They've been uploaded 7-12 minutes ago from concurrent jobs in different systems. So it's a race condition: the rest of the jobs are likely still running and will publish more dists soon. It's a duplicate of #50. I think we can patch it in this repo by adding |
It looks like their prior two releases only published 3.6 wheels as well. |
Oh wow! You're right! |
... so maybe it just needs an upgraded pip? |
Yes, looks like it. |
@virtuald could you verify that |
Works here. See https://github.com/MirahezeBots/MirahezeBots/pull/391/checks?check_run_id=1856702005 |
Works for me, thanks! |
FTR I've pushed a tag v1.4.2 but can't publish it to the marketplace until @pradyunsg re-accepts the marketplace dev agreement. |
Oh yes.
https://github.com/robotpy/robotpy-navx/runs/1856441423?check_suite_focus=true
Seems like the crptography project messed something up when publishing their wheel? But maybe you need to set that environment variable mentioned?
The text was updated successfully, but these errors were encountered: