-
Notifications
You must be signed in to change notification settings - Fork 0
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 upgrade fails to update Cadabra 2.4.2.4 -> 2.4.4.1 #4
Comments
Yeah, I know. I spent 5 minutes updating the homebrew package to the latest cadabra version, and then two hours trying to figure out why this happens. I have no idea so far, but it looks like the homebrew people messed up something. I don't have time to dig into this further, any help is welcome (if not I will probably remove the homebrew package altogether as it is just causing headaches). |
I will let you know if I figure out a fix. |
Is there an update on this? I am also having trouble building from source when I run the last step. This worked in the past for the previous version 2.4.2.4 but I have the following error for the latest version 2.4.4.1:
|
I can't help with the homebrew problem, they messed something up or changed something in a backward incompatible way and I do not have time to dig into that. When you build from source and do |
Thanks for your response, Kasper. I do literally what you suggested
So I do |
Some weird permissions on your
give? |
That gives
What should the normal permissions be? |
What does
give? |
brew upgrade
is failing to upgrade Cadabra.Things I tried but which failed
brew cleanup
brew cleanup --prune=1
sudo chown -R <user> /opt/homebrew
sudo brew upgrade
(not supported anymore)This is a single-user Mac system and I do have admin privileges. However, the standard online remedies for a
CMake
error inbrew
did not cure the ailment.I am fairly certain this is just a
brew
problem with privileges and not a Cadabra issue, but I've never faced it in a form that wouldn't get fixed after usingchown
.The text was updated successfully, but these errors were encountered: