Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Hack5190

macrumors 6502a
Original poster
Keeping the TigerBrew database updated is normally done with the command:

brew update

Due to changes I made to a formula - some things on my system got broken 😳.

The internal diagnostic tool (brew doctor) was not able to identify or fix the issue.

Fear not - you can force an update of the TigerBrew database with these commands:

cd `brew --prefix`
git remote add origin https://github.com/mistydemeo/tigerbrew
git fetch origin
git reset --hard origin/master
 
Can you post more details about what is broken? What error messages are you getting?
The only thing broken was what I broke 🙄. The recipe for the program I was trying to brew used an old version of code. So I edited the recipe to use the latest version. When finished I deleted the recipe thinking that brew update would download the original, it didn't. And there you have it @Intell
 
That's a bit too vague. What exactly did you do. What did you edit, how did you edit it, what did you change in it?
 
That's a bit too vague. What exactly did you do. What did you edit, how did you edit it, what did you change in it?

Brew (and TigerBrew) have a directory with scripts that are used when downloading and compiling (aka: brewing) each of the 'add ons'. These files / scripts are called recipes. The recipe for the program I was trying to brew, dnscrypt, used a version behind the current version. I edited the recipie to download the current version (including editing the checksum). As I mentioned deleting the recipe and running brew update didn't replace the delete recipe.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.