Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

undefined: setCompactionCommited

undefined: setCompactionCommited

Process completed with exit code 2.

Failed to restore: "/usr/local/bin/gtar" failed with error: The process '/usr/local/bin/gtar' failed with exit code 2

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v4, actions/[email protected], actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

libomp 19.1.0 is already installed and up-to-date. To reinstall 19.1.0, run: brew reinstall libomp

ninja 1.12.1 is already installed and up-to-date. To reinstall 1.12.1, run: brew reinstall ninja

openblas 0.3.28 is already installed and up-to-date. To reinstall 0.3.28, run: brew reinstall openblas

pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config

You are using macOS 12. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version. It is expected behaviour that Homebrew will be buggy and slow. Do not create any issues about this on Homebrew's GitHub repositories. Do not create any issues even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help in Homebrew's discussions but are unlikely to receive a response. Try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it.