WheelFileValidationError with furo package only on the poetry==1.4.1 #639
-
Copied from an issue reported on Poetry's GitHub repo that was then closed in favor of bringing the discussion here. It seems that there is a WheelFileValidationError when installing furo using poetry 1.4.1, but not 1.4.0. I'm wondering if it's caused by an incorrect hash in the latest version of furo that could be fixed by updating the latest wheel for furo. Original issue link: python-poetry/poetry#7691 (comment) |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 9 replies
-
Is this related to pradyunsg/sphinx-theme-builder#13? |
Beta Was this translation helpful? Give feedback.
-
This should be resolved with the release I just cut right now. :) |
Beta Was this translation helpful? Give feedback.
-
I'm still seeing this error with the 2023.03.23 version (as it looks like @doyled-it also was in that output). |
Beta Was this translation helpful? Give feedback.
-
Getting error in 2023.03.23 version, poetry output in gist here |
Beta Was this translation helpful? Give feedback.
-
Can someone confirm that the latest release (2023.03.27) fixes this? |
Beta Was this translation helpful? Give feedback.
-
Alrighty. What happened here is sphinx-theme-builder was generating the wrong hashes and fixing Furo's hashes required me to cut a release of sphinx-theme-builder then cut a release of Furo. I'd assumed that I'd cut a release of sphinx-theme-builder already, but hadn't. Once that was fixed there and a release was made, Furo merely needed a rebuild and release -- which is what 2023.03.27 is. Thanks for flagging this! :) |
Beta Was this translation helpful? Give feedback.
Alrighty. What happened here is sphinx-theme-builder was generating the wrong hashes and fixing Furo's hashes required me to cut a release of sphinx-theme-builder then cut a release of Furo. I'd assumed that I'd cut a release of sphinx-theme-builder already, but hadn't. Once that was fixed there and a release was made, Furo merely needed a rebuild and release -- which is what 2023.03.27 is.
Thanks for flagging this! :)