You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An update to the version requirement for Python3 setuptools is breaking Docker-based builds:
/tmp/pip-build-env-1trg79qq/overlay/local/lib/python3.10/dist-packages/setuptools_scm/_integration/setuptools.py:31: RuntimeWarning:
ERROR: setuptools==59.6.0 is used in combination with setuptools-scm>=8.x
Your build configuration is incomplete and previously worked by accident!
setuptools-scm requires setuptools>=61
I've tried a couple of workarounds to uninstall either python3-setuptools or python3-pip and nothing is working:
pip3 install --upgrade setuptools==61.0.0 installs setuptools 61.0.0 in /usr/local/lib/python3.10/dist-packages, but leaves version 59.6.0 in /usr/lib/python3/dist-packages/setuptools. The 59.6.0 version is then used during AT requirements installation and fails
Uninstalling setuptools and then re-installing pip3 ends up reinstalling setuptools 59.6.0, so back to same situation as bullet 1 above.
However I see some error messages that are worth looking into:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
grpcio-status 1.70.0 requires protobuf<6.0dev,>=5.26.1, but you have protobuf 3.20.3 which is incompatible.
Subject
[Build] for compilation-related issues.
Describe the bug
An update to the version requirement for Python3 setuptools is breaking Docker-based builds:
I've tried a couple of workarounds to uninstall either python3-setuptools or python3-pip and nothing is working:
pip3 install --upgrade setuptools==61.0.0
installs setuptools 61.0.0 in /usr/local/lib/python3.10/dist-packages, but leaves version 59.6.0 in /usr/lib/python3/dist-packages/setuptools. The 59.6.0 version is then used during AT requirements installation and fails@vvbandeira / @luarss , any ideas?
Expected Behavior
Functioning docker build like before
Environment
To Reproduce
Here's the Dockerfile that was working previously
To reproduce:
docker build -t autotuner:1.0 -f Dockerfile .
Relevant log output
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: