raulcd opened a new issue, #40546: URL: https://github.com/apache/arrow/issues/40546
### Describe the bug, including details regarding any error messages, version, and platform. When running the binary verification task [verify-rc-binaries-wheels-macos-11-arm64](https://github.com/ursacomputing/crossbow/actions/runs/8274331154/job/22639503461#step:4:181) we had the following error: ``` ==> Checking for dependents of upgraded formulae... ==> Reinstalling 1 dependent with broken linkage from source: node@14 Error: node@14 has been disabled because it is not supported upstream! ==> Caveats ==> meson zsh completions have been installed to: /opt/homebrew/share/zsh/site-functions Upgrading meson has failed! Using vala Homebrew Bundle failed! 1 Brewfile dependency failed to install. Error: Process completed with exit code 1. ``` The issue [was solved by manually updating the workflow file](https://github.com/ursacomputing/crossbow/actions/runs/8278634741/job/22651393444) forcing node@20 before installing the cpp/Brewfile: ```diff $ git diff diff --git a/dev/tasks/verify-rc/github.macos.arm64.yml b/dev/tasks/verify-rc/github.macos.arm64.yml index fce1092..e903973 100644 --- a/dev/tasks/verify-rc/github.macos.arm64.yml +++ b/dev/tasks/verify-rc/github.macos.arm64.yml @@ -43,11 +43,11 @@ jobs: TEST_DEFAULT: 0 TEST_{{ target|upper }}: 1 run: | - brew bundle --file=arrow/cpp/Brewfile - brew bundle --file=arrow/c_glib/Brewfile # Force node v20 due to GH-39469 brew install node@20 export PATH="$(brew --prefix node@20)/bin:$PATH" + brew bundle --file=arrow/cpp/Brewfile + brew bundle --file=arrow/c_glib/Brewfile export PATH="$(brew --prefix ruby)/bin:$PATH" export PKG_CONFIG_PATH="$(brew --prefix ruby)/lib/pkgconfig" arrow/dev/release/verify-release-candidate.sh \ ``` ### Component(s) Continuous Integration, Release -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
