3 ms·
Be aware of "update bug" If Homebrew was updated on Aug 10-11th 2016 and brew update always says "Already up-to-date". you need to run: ``` cd "$(brew --repo)
by mirekrusin 10y ago
Be aware of "update bug"
If Homebrew was updated on Aug 10-11th 2016 and brew update always says "Already up-to-date". you need to run:
```
cd "$(brew --repo)" && git fetch && git reset --hard origin/master && brew update
```
I had to.
- OskarS 10y agoYep, me as well. Thanks!
- wonks 10y agoI also had to do this. Keep in mind that ```brew update``` might take a while to output anything when you do this (it did for me), and then it will ask you to wait while it migrates to a new directory.
- oefrha 10y agoJust want to point out that you could always add the --verbose flag to brew commands to see more progress information (in this case how brew calls git to update brew itself and each tap you have tapped, including the core tap).
- Bhullnatik 10y agoIt took me way too long of daily `brew update`s to notice something was wrong.
- tracker1 10y agoit's funny, but other than a few basic tools, most of what I get from homebrew is versionables (nvm, pyenv, etc) of other programming utilities, in that, I don't run brew update very often, usually only before installing something new via homebrew.
- STRML 10y agoYep, had to too. They released a revision with a broken update fn? Or did they force-push?