-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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 tries to use already deleted portable-ruby #5707
Comments
Same issue. I was able to successfully re-run the post-installs by first manually installing portable-ruby. |
@CommanderTso do you have a simple explanation on how to manually install portable-ruby? I'd greatly appreciate it. |
Hey @Amit-PivotalLabs - I used |
|
Thanks @CommanderTso that was super helpful, worked right away. |
What you were trying to do (and why)
brew upgrade
What happened (include command output)
So basically running
brew upgrade
deleted portable-ruby (I guess because my system also hasruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-darwin16]
available), but the install steps after the cleanup now tried to use the ruby that was already deleted.Command output
What you expected to happen
The script should have used the newer system ruby instead of the portable-ruby that had already been deleted.
The text was updated successfully, but these errors were encountered: