Scheduled Latest Vagrant Boxes verification #108
Annotations
1 error and 13 warnings
Run technote-space/create-pr-action@v2.1.4
There is a failed process.
|
The macOS-12 environment is deprecated, consider switching to macOS-13, macOS-14 (macos-latest) or macOS-15. For more details, see https://github.com/actions/runner-images/issues/10721
|
Run technote-space/create-pr-action@v2.1.4
>> fatal: refusing to merge unrelated histories
|
Run technote-space/create-pr-action@v2.1.4
>> ==> vagrant: A new version of Vagrant is available: 2.4.3 (installed version: 2.4.1)!
|
Run technote-space/create-pr-action@v2.1.4
>> ==> vagrant: To upgrade visit: https://www.vagrantup.com/downloads.html
|
Run technote-space/create-pr-action@v2.1.4
>> The box you requested to be removed could not be found. No
|
Run technote-space/create-pr-action@v2.1.4
>> boxes named 'centos/7' could be found.
|
Run technote-space/create-pr-action@v2.1.4
>> The box you requested to be removed could not be found. No
|
Run technote-space/create-pr-action@v2.1.4
>> boxes named 'centos/8' could be found.
|
Run technote-space/create-pr-action@v2.1.4
>> The box you requested to be removed could not be found. No
|
Run technote-space/create-pr-action@v2.1.4
>> boxes named 'generic/ubuntu1604' could be found.
|
Run technote-space/create-pr-action@v2.1.4
>> The box you requested to be removed could not be found. No
|
Install vagrant tool
Not upgrading vagrant, the latest version is already installed
|
Install vagrant tool
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