Error: [email protected]: unknown version :mountain_lion

Question

Followed this tutorial in installing qt5.5 on a macOS version 10.13.6 High Sierra. Failed when trying to brew install [email protected] giving me an error below:

Error: [email protected]: unknown version :mountain_lion

Versions:

• brew
  Homebrew 2.0.0
  Homebrew/homebrew-core (git revision 175af; last commit 2019-02-02)
  Homebrew/homebrew-cask (git revision 05a81; last commit 2019-02-02)

• macOS version 10.13.6 High Sierra

any help?

Cangue

Answer 1

Referring to the tutorial, the following steps are executed to install [email protected]

brew update
cd $( brew --prefix )/Homebrew/Library/Taps/homebrew/homebrew-core

# below is the last commit containing [email protected] with homebrew
git checkout 9ba3d6ef8891e5c15dbdc9333f857b13711d4e97 Formula/[email protected]

# here is where the error occurs
brew install [email protected]

Solution

turns out line 25 of [email protected] formula file checked out in the command ( as seen in the referred tutorial)

git checkout 9ba3d6ef8891e5c15dbdc9333f857b13711d4e97 Formula/[email protected]

is causing this problem. commenting it out fixes the issue

Cangue

@ChrisHough what is the error you see when you run brew install [email protected] after commenting out line 25 of the file mentioned above? – Cangue

I was finding it difficult to find the actual file. On my device, it is located in /usr/local/opt/[email protected]/.brew and I had to comment out line #69 – Circulation

@Circulation .brew is empty for me, is there another location? – Measly

@ChrisHough .brew is a dot directory. What do you get hit ls -a (in the [email protected] directory)? – Circulation

@Circulation I was able to find it at /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/[email protected] however, I have noticed this disappear when I run brew update and brew upgrade – Measly

/usr/local/opt/[email protected]/.brew/[email protected] Look for depends_on - Line 16 for me – Overcrop

This works for me too, but as @ChrisHough mentioned, the problem reoccurs after running brew update. – Appall