-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Old ~/.gem folder breaks brew audit after OS upgrade #3355
Comments
Closing this for now but will investigate further if it crops up more. CC @reitermarkus this may be another argument for using bundler for more of this stuff. |
I just had this gem issue pop again on a system running 10.11, though it wasn't after an OS upgrade. It initially was failing only with Here's some of the console error messages I was seeing (though it's now fixed).
After deleting
but then |
If removing
should work. |
tl;dr I had a problem, found a solution, posting the solution here. Maintainers may close this issue if they don't think there's anything else to do.
Please always follow these steps:
brew
command and notbrew install
ing or the post-install behaviour of one or more formulae? If it's a formulae-specific problem please file this issue at the relevant tap e.g. for Homebrew/homebrew-core https://github.com/Homebrew/homebrew-core/issues/newbrew update
and retried your prior step?brew doctor
, fixed all issues and retried your prior step?brew config
andbrew doctor
and included their output with your issue?I was trying to audit a formula (ie.
brew audit boost
).This normally works of course, and and it works on one of my 3 CI machines, but 2 of 3 were failing to find the rainbow gem when invoking
brew audit
directly (brew test-bot
doesn't have this problem):I realized that the two machines experiencing this problem had recently had OS upgrades (to 10.12 and 10.13). Our 10.11 machine hasn't had a major OS upgrade and still works fine. Renaming the
~/.gem
folder to~/.gem_old
fixed the problem for me. Deleting it is an option as well, but it is at your own risk. I may also have a problem with environment variables I suppose.I searched for this error message and wasn't able to find anyone else who had this problem. I was expecting an issue like this to exist so people could see the problem and a possible solution. I suppose a
brew doctor
complaint could be helpful as well or araise
message saying that the~/.gem
folder may be out of date if the OS is upgraded.Step-by-step reproduction instructions (by running
brew
commands)~/.gem
brew audit boost
I haven't tried reproducing this since I figured out the solution, so I don't know if it will still happen or if it was a transient issue from when I upgraded my machines (in the month before High Sierra was released). You can close the issue if you don't want to take further action, but I can help debug this further or work on a pull request to document the issue, as I still have the old
~/.gem
folder on one of my CI machines.The text was updated successfully, but these errors were encountered: