-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
brew upgrade fails for Python's 2to3 conflict #2322
Comments
Running into the same issue in Envoy CI |
Looks like it is coming from the system python?
|
Most likely caused by #2217 where we switched Python 2 installation from to official pkg. This pkg brings this symlink and brew can't override it later |
@miketimofeev I guess we should leave default MacOS Python 2 without any updates (just install pip) to avoid issues with brew |
@maxim-lobanov there are some issues with pip installation in this case. I suggest removing the 2to3 symlink created by python2 before the python3 installation. |
Thanks a lot @miketimofeev @maxim-lobanov ! |
adds the `rm -rf /usr/local/bin/2to3` workaround as suggested in actions/runner-images#2322
adds the `rm -rf /usr/local/bin/2to3` workaround as suggested in actions/runner-images#2322
* starts 2.3.0 release cycle updates versions in the configuration tools, bumps up copyright dates (also normalizes the MIT license to make it recognizable for github), and updates the release.sh script for the release automation. * fixes build on macOS adds the `rm -rf /usr/local/bin/2to3` workaround as suggested in actions/runner-images#2322
- brew install octave failing due to trouble overwriting things installed by existing versions of python and gcc. Ref: actions/runner-images#2322 Ref: actions/runner-images#2391
* Add rm '/usr/local/bin/2to3' in macOS jobs to fix symlink issue when brew upgrades Python (cf actions/runner-images#2322) * Add brew upgrade step preceded by unlinking gcc@8 and gcc@9 due to other symlink failures (cf actions/runner-images#2391)
This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#6507 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#6507 Ref: actions/runner-images#2322
CI has started failing again recently and I found this solution while going over: actions/runner-images#2322
CI has started failing again recently and I found this solution while going over: actions/runner-images#2322
The github mac runner images added python 3.11 but, unlike 3.10, not via brew. This causes brew install to fail with link conflict errors now that boost-python3 switched over to 3.11. Workaround this, and future python brew link errors, by ovewriting all links for python packages. Homebrew/homebrew-core@8c79089 https://github.com/orgs/Homebrew/discussions/3895 actions/setup-python#577 actions/runner-images#6459 actions/runner-images#6507 actions/runner-images#2322
The github mac runner images added python 3.11 but, unlike 3.10, not via brew. This causes brew install to fail with link conflict errors now that boost-python3 switched over to 3.11. Workaround this, and future python brew link errors, by overwriting all links for python packages. Homebrew/homebrew-core@8c79089 https://github.com/orgs/Homebrew/discussions/3895 actions/setup-python#577 actions/runner-images#6459 actions/runner-images#6507 actions/runner-images#2322
MacOS CI build started to fail in the PRs because when upgrading python it was not possible to override one existing file (related to 2to3 package). Apparently this happens because MacOS runners some times have python versions not installed/compatible with brew. Example of the failure: https://github.com/coturn/coturn/actions/runs/3850951324 The proposed workaround is taken from here: actions/runner-images#2322
The github mac runner images added python 3.11 but, unlike 3.10, not via brew. This causes brew install to fail with link conflict errors now that boost-python3 switched over to 3.11. Workaround this, and future python brew link errors, by overwriting all links for python packages. Homebrew/homebrew-core@8c79089 https://github.com/orgs/Homebrew/discussions/3895 actions/setup-python#577 actions/runner-images#6459 actions/runner-images#6507 actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#6507 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#6507 Ref: actions/runner-images#2322
This is still an issue. Can it be reopened or should I create a new issue? |
Description
If I run the commands
brew update
andbrew upgrade
, the job fails. This is similar to #2248 and #1811, but the specific error is different and is probably due to some other Python being installed.Area for Triage:
Question, Bug, or Feature?:
Bug
Virtual environments affected
Expected behavior
I would expect that brew upgrade works fine.
Actual behavior
brew upgrade
is failing with error:Repro steps
Run the following commands in a macos image:
brew update
brew upgrade
See https://github.com/traversaro/github-actions-brew-update-upgrade-check/actions/runs/435789601 for a minimal job that is failing.
The text was updated successfully, but these errors were encountered: