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
Error: cannot load such file -- nokogiri
on livecheck run
#11486
Comments
I just merged a Dependabot PR to upgrade |
I had this in an upgrade run before, so I don't think it's really missing:
|
@SMillerDev Is nokogiri in |
|
Does this work around the issue? It did for me. HOMEBREW_FORCE_VENDOR_RUBY=1 brew livecheck --installed --newer-only I hit this too, seems only to happen for |
Forcing a vendor ruby did not help, but |
It should be:
(yes, we know this doesn't work on arm64 - that is a RubyGems issue) |
Any reason my macOS could have installed a nokogiri without a platform? |
Not sure. The one you have should be the default if it can't find a matching platform (but our load path stuff won't pick this up atm - it only handles You could try |
It does, nokogiri gets installed again without a platform specification. |
What does |
|
Should be fine. (Though weirdly, Darwin 14 is the Portable Ruby platform but your |
Likely because I ran #11486 (comment) since making the issue. |
At this point I think the appropriate solution is to remove the use of |
I've been working on fixing/improving parts of the I've been planning to add a generic Edit: I now have this implemented locally and I'm working on putting the finishing touches on it before creating a PR. |
😍 sounds great @samford! |
brew config
outputbrew doctor
outputbrew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
run
brew livecheck --installed --newer-only
to update software in brew.What happened (include all command output)?
What did you expect to happen?
return outdated software
Step-by-step reproduction instructions (by running
brew
commands)`brew livecheck --installed --newer-only`
The text was updated successfully, but these errors were encountered: