some more little fixes and improvements #310
Annotations
2 errors and 11 warnings
Install deps
The `brew link` step did not complete successfully
|
Install deps
Process completed with exit code 1.
|
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
|
Install deps
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.
|
Install deps
gettext 0.22.5 is already installed and up-to-date.
To reinstall 0.22.5, run:
brew reinstall gettext
|
Install deps
freetype 2.13.3 is already installed and up-to-date.
To reinstall 2.13.3, run:
brew reinstall freetype
|
Install deps
gmp 6.3.0 is already installed and up-to-date.
To reinstall 6.3.0, run:
brew reinstall gmp
|
Install deps
jpeg-turbo 3.0.4 is already installed and up-to-date.
To reinstall 3.0.4, run:
brew reinstall jpeg-turbo
|
Install deps
libogg 1.3.5 is already installed and up-to-date.
To reinstall 1.3.5, run:
brew reinstall libogg
|
Install deps
libpng 1.6.44 is already installed and up-to-date.
To reinstall 1.6.44, run:
brew reinstall libpng
|
Install deps
libvorbis 1.3.7 is already installed and up-to-date.
To reinstall 1.3.7, run:
brew reinstall libvorbis
|
Install deps
zstd 1.5.6 is already installed and up-to-date.
To reinstall 1.5.6, run:
brew reinstall zstd
|
Install deps
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.
|
Loading