mirror of
https://github.com/openhwgroup/cve2.git
synced 2025-04-20 12:08:05 -04:00
[ci] Force setuptools not to use version 50.0.0 for now
There's a long and painful discussion on the setuptools issues list (I count 9 issues raised the day after the release). This is all to do with how Debian/Ubuntu installs stuff with pip. There's an "official" workaround that involves setting things in your environment, but that looks a bit fiddly with the Azure pipelines stuff and this has been such a disaster that I'm pretty certain the setuptools maintainers will release something more sensible soon. See e.g. https://github.com/pypa/setuptools/issues/2350#issuecomment-683512526 for a careful description of what's going on.
This commit is contained in:
parent
f30e84ba00
commit
3703a3ad8e
1 changed files with 7 additions and 1 deletions
|
@ -66,7 +66,13 @@ case "$ID-$VERSION_ID" in
|
|||
# an older version of a package must be used for a certain Python version.
|
||||
# If that information is not read, pip installs the latest version, which
|
||||
# then fails to run.
|
||||
$SUDO_CMD pip3 install -U setuptools pip six
|
||||
$SUDO_CMD pip3 install -U pip six
|
||||
|
||||
# There's been a bit of a kerfuffle about setuptools version 50, which
|
||||
# breaks importing distutils on Debian/Ubuntu systems. Make sure we don't
|
||||
# pick it up until the dust has settled and things work again.
|
||||
$SUDO_CMD pip3 install -U 'setuptools < 50.0.0'
|
||||
|
||||
$SUDO_CMD pip3 install -U -r python-requirements.txt
|
||||
|
||||
# Install Verible
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue