Skip to content
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

macOS Homebrew CI failing #565

Closed
traversaro opened this issue Dec 21, 2020 · 1 comment · Fixed by #566
Closed

macOS Homebrew CI failing #565

traversaro opened this issue Dec 21, 2020 · 1 comment · Fixed by #566

Comments

@traversaro
Copy link
Member

Since 3 days ago (last successful build is https://github.com/robotology/robotology-superbuild/actions/runs/429511263) the macOS Homebrew build is failing with:

2020-12-21T02:37:53.3978400Z �[32m==>�[0m �[1mInstalling glib dependency: �[32mpython@3.9�[39m�[0m
2020-12-21T02:37:53.3979430Z �[34m==>�[0m �[1mPouring python@3.9-3.9.1_1.catalina.bottle.tar.gz�[0m
2020-12-21T02:37:59.5404030Z �[31mError:�[0m The `brew link` step did not complete successfully
2020-12-21T02:38:00.2855040Z The formula built, but is not symlinked into /usr/local
2020-12-21T02:38:00.2855590Z Could not symlink bin/2to3
2020-12-21T02:38:00.2856080Z Target /usr/local/bin/2to3
2020-12-21T02:38:00.2856530Z already exists. You may want to remove it:
2020-12-21T02:38:00.2857700Z   rm '/usr/local/bin/2to3'
2020-12-21T02:38:00.2858370Z 
2020-12-21T02:38:00.2858830Z To force the link and overwrite all conflicting files:
2020-12-21T02:38:00.2859760Z   brew link --overwrite python@3.9
2020-12-21T02:38:00.2860080Z 
2020-12-21T02:38:00.2860450Z To list all files that would be deleted:
2020-12-21T02:38:00.2861310Z   brew link --overwrite --dry-run python@3.9
2020-12-21T02:38:00.2861650Z 
2020-12-21T02:38:00.2862410Z Possible conflicting files are:
2020-12-21T02:38:00.2863770Z /usr/local/bin/2to3 -> /Library/Frameworks/Python.framework/Versions/2.7/bin/2to3

Fortunately we now have the conda-forge-based CI, so we should catch macOS regressions even if we do not immediately fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant