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

Update nokogiri to at least 1.6.7 #27

Closed
wants to merge 1 commit into from

Conversation

jroweboy
Copy link

First off, sorry for the flood of pull requests I'm about to open. These are some changes that I made in order to get this plugin to work with our configuration.

Nokogiri in ruby 2.2 does not support Windows, and vagrant recently just
merged a pull request to update the dependency to 1.6.7
(See hashicorp/vagrant#6848 for more details)
This update enables people to use this plugin on windows with the most recent
versions of vagrant. This should wait to be merged until the patch for vagrant
is released.

Nokogiri in ruby 2.2 does not support Windows, and vagrant recently just
merged a pull request to update the dependency to 1.6.7
(See hashicorp/vagrant#6848)
This update enables people to use this plugin on windows with the most recent
versions of vagrant. This should wait to be merged until the patch for vagrant
is released.
@jonludlam
Copy link
Collaborator

Thanks for this. As you suggest, I'll leave this open for now.

@darkn3rd
Copy link

darkn3rd commented May 3, 2016

👍

@jroweboy
Copy link
Author

jroweboy commented Jul 6, 2016

@jonludlam Just a reminder that this is still an issue. I forgot to let you know that vagrant has released a dot version that contains the related fix hashicorp/vagrant@9af8266 (The fix is in both 1.8.3 and 1.8.4) Either my fix, or the more involved #30 could work, and I don't really know what the right way to handle this is.

@jroweboy jroweboy closed this Nov 7, 2016
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

Successfully merging this pull request may close these issues.

3 participants