Skip to content

CI

CI #4410

Triggered via schedule November 25, 2024 02:31
Status Success
Total duration 15m 9s
Artifacts

ci.yml

on: schedule
activate
0s
activate
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
build (macos-12, 3.3)
Cannot link ghostscript Another version is already linked: /usr/local/Cellar/ghostscript/10.02.1
build (macos-12, 3.3)
A brownout will take place on November 25, 14:00 UTC - November 26, 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
build (macos-12, 3.3)
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.
build (macos-12, 3.3)
ghostscript 10.04.0 is available and more recent than version 10.02.1.
build (macos-12, 3.3)
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.