-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Latest pip release fails #6554
Comments
Hi, you can force a clean installation by wiping the environment https://docs.readthedocs.io/en/stable/guides/wipe-environment.html That will download the latest pip instead of using one from cache |
Brilliant - thanks so much for the quick reply :) |
Hi,
|
@Aricg that's weird. Did you wipe only once? I can think of a reason where the wipe didn't propagate to all servers. |
@stsewd I have done it multiple times to both stable and master to try to make it "take" |
@Aricg can you please trigger a wipe for latest but don't trigger any build. I want to check the servers for something |
Like @Aricg in the last day or so I have tried wipe only for the problem to recur: It looks like the fix for #6571 was merged about 25 minutes ago, so hopefully the fix will go live shortly. |
@peterjc probably it will be live next week |
Thanks - I'll do a manual wipe as needed until then. |
Is it possible to do a manual wipe for pull requests? I can't find a way to do so. |
@johannfaouzi currently, no. We don't support that yet. |
This is breaking this PR cobbler/cobbler#2254 The build environment cannot be wiped because this is (at least to my knowledge) not possible on PR's. |
@SchoolGuy see #6566 |
Details
Expected Result
Build without failing ... :)
Actual Result
Currently all builds are failing because the automatic upgrade (since #4823 ) to pip 20.0 was buggy (see pypa/pip#7620 ). There's now a 20.0.1 release which seems to have fixed the problem for others ... but how can I force my readthedocs to also upgrade to the .1 version?
The text was updated successfully, but these errors were encountered: