Description
- are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
- ran a
brew
command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's abrew cask
problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap. - ran
brew update
and can still reproduce the problem? - ran
brew doctor
, fixed all issues and can still reproduce the problem? - ran
brew config
andbrew doctor
and included their output with your issue?
What you were trying to do (and why)
I tried to run brew update --quiet
in Travis and Azure Pipelines. This is actually what git.git does for ages, and it broke recently. It is also what Git for Windows does, and it also broke recently.
What happened (include command output)
Command output
$ brew update --quiet Usage: brew update_report [--preinstall]The Ruby implementation of brew update. Never called manually.
--preinstall Run in 'auto-update' mode (faster, less output). -f, --force Override warnings and enable potentially unsafe operations. -d, --debug Display any debugging information. -v, --verbose Make some output more verbose. -h, --help Show this message.
Error: invalid option: --quiet
What you expected to happen
I expected no output and no failure, as e.g. here.
[EDIT] It was pointed out that there is output (despite what one might expect of --quiet
), as can easily be seen by the linked log output. But it did succeed previously, and now it fails.
Step-by-step reproduction instructions (by running brew
commands)
brew update --quiet
For your convenience, I set up https://github.com/dscho/brew-update-quiet-mcve which is hooked up to an Azure Pipeline running the command (see latest build output), including PR builds (read: you can trigger new builds by editing azure-pipelines.yml
and opening a Pull Request).