Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

brew install is broken #1438

Open
joshavant opened this issue Sep 23, 2024 · 0 comments
Open

brew install is broken #1438

joshavant opened this issue Sep 23, 2024 · 0 comments

Comments

@joshavant
Copy link

joshavant commented Sep 23, 2024

I'm on macOS 14.1.1 with Xcode 15.4 on an M1 Max CPU.

Doing this in Terminal:
brew install --HEAD mtg/essentia/essentia

Yields this:

==> /opt/homebrew/opt/[email protected]/bin/python3 waf configure --mode=release --with-examples --with-vamp
Last 15 lines from /Users/joshavant/Library/Logs/Homebrew/essentia/01.python3:
2024-09-23 23:33:37 +0000

/opt/homebrew/opt/[email protected]/bin/python3
waf
configure
--mode=release
--with-examples
--with-vamp
--prefix=/opt/homebrew/Cellar/essentia/HEAD-a770d1b


If reporting this issue please do so at (not Homebrew/brew or Homebrew/homebrew-core):
  https://github.com/mtg/homebrew-essentia/issues

Warning: Unable to query GitHub for recent issues on the tap
GitHub API Error: Bad credentials
The GitHub credentials in the macOS keychain may be invalid.
Clear them with:
  printf "protocol=https\nhost=github.com\n" | git credential-osxkeychain erase
essentia's formula was built from an unstable upstream --HEAD.
This build failure is expected behaviour.
Do not create issues about this on Homebrew's GitHub repositories.
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.

Unfortunately, I can't personally speak much to this error output. Happy to help if there are any leading questions.

As a new user to this project, with this issue and #1439, I don't see a clear way for any new users to adopt this project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant