Clarify usage of history variables in error messages #10501
pull-request-checks.yaml
on: pull_request
check-ubuntu-20_04-make-gcc
19m 5s
check-ubuntu-20_04-make-clang
23m 2s
check-ubuntu-20_04-make-clang-smt-z3
4m 4s
check-ubuntu-20_04-cmake-gcc
16m 39s
check-ubuntu-22_04-make-clang
17m 31s
check-ubuntu-22_04-cmake-gcc
29m 12s
check-ubuntu-24_04-cmake-gcc-14
16m 37s
check-ubuntu-22_04-cmake-gcc-32bit
14m 48s
check-ubuntu-20_04-cmake-gcc-KNOWNBUG
3m 8s
check-ubuntu-20_04-cmake-gcc-THOROUGH
10m 26s
check-macos-13-make-clang
32m 34s
check-macos-12-cmake-clang
36m 38s
check-vs-2019-cmake-build-and-test
31m 31s
check-vs-2022-make-build-and-test
19m 36s
windows-msi-package
6m 27s
check-string-table
2m 7s
check-docker-image
21m 43s
include-what-you-use
22m 59s
Annotations
6 warnings
check-macos-12-cmake-clang
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
check-macos-12-cmake-clang
cmake 3.30.3 is already installed and up-to-date.
To reinstall 3.30.3, run:
brew reinstall cmake
|
check-macos-12-cmake-clang
ninja 1.12.1 is already installed and up-to-date.
To reinstall 1.12.1, run:
brew reinstall ninja
|
check-macos-12-cmake-clang
maven 3.9.9 is already installed and up-to-date.
To reinstall 3.9.9, run:
brew reinstall maven
|
check-macos-12-cmake-clang
bison 3.8.2 is already installed and up-to-date.
To reinstall 3.8.2, run:
brew reinstall bison
|
check-macos-12-cmake-clang
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.
|