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

Enlarge description of gem pristine #388

Open
DcsMarionDickten opened this issue Jan 31, 2025 · 0 comments
Open

Enlarge description of gem pristine #388

DcsMarionDickten opened this issue Jan 31, 2025 · 0 comments

Comments

@DcsMarionDickten
Copy link

I updated my system and started getting warnings of the kind "Nokogiri was built against LibXML version 2.7.8, but has dynamically loaded 2.9.0". After some googling I found someone recommended using gem pristine to fix this. I looked up the documentation for this command and couldn't see at all how "Restores installed gems to pristine condition from files located in the gem cache" would help, as files in the gem cache would still be the same because I didn't make any changes. I read the detailed decription too but did not see how that would affect my case since, again, I did not modify the gem.

In the end I tried the command and to my astonishment it recompiled the native extension, indeed fixing the problem. Since people upgrade their system all the time, would it make sense to document how gem pristine helps updating gems with native extensions after a system update? "pristine" is a bit of a misnomer in this case, so this command is not an intuitive candidate for a solution.

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