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

instiki on windows requires nokogiri 1.7.2? #53

Closed
omicroncz opened this issue Nov 22, 2017 · 2 comments
Closed

instiki on windows requires nokogiri 1.7.2? #53

omicroncz opened this issue Nov 22, 2017 · 2 comments

Comments

@omicroncz
Copy link

omicroncz commented Nov 22, 2017

Hi,
When running the
ruby bundle install --path vendor/bundle
on a Windows 7 machine it tries to install nokogiri 1.7.2 (see output below)
I think there are some compatibility issues between nokogiri 1.7.2 and ruby2.4 for windows machines but it was solved with the nokogiri 1.8.1 release which I can successfully install.

Is there a way to make the bundle install use the 1.8.1 version instead ?

Fetching gem metadata from http://rubygems.org/......... Using rake 10.4.2 Using RedCloth 4.3.2 Using abstract 1.0.0 Using bundler 1.16.0 Using daemons 1.2.5 Using erubis 2.7.0 Using eventmachine 1.2.5 (x64-mingw32) Using file_signature 1.2.0 Using iconv 1.0.4 Using itextomml 1.5.6 Using json 2.1.0 Using mini_portile2 2.1.0 Fetching nokogiri 1.7.2 (x64-mingw32) Installing nokogiri 1.7.2 (x64-mingw32) Gem::RuntimeRequirementNotMetError: nokogiri requires Ruby version < 2.4, >= 2.1.0. The current ruby version is 2.4.0. An error occurred while installing nokogiri (1.7.2), and Bundler cannot continue. Make sure that gem install nokogiri -v '1.7.2' succeeds before bundling. In Gemfile: maruku was resolved to 0.7.3.beta1, which depends on nokogiri

Thanks

@distler
Copy link
Collaborator

distler commented Nov 22, 2017

Is there a way to make the bundle install use the 1.8.1 version instead ?

Sure. Just edit that line in the Gemfile.

I haven't tested Instiki with 1.8.1 yet, but I expect it should work fine. Let me know if it does.

@distler
Copy link
Collaborator

distler commented Jun 23, 2018

This commit should fix the issue.

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

2 participants