Open ringods opened 10 years ago
Same problem on MacOS X:
ERROR root: -- Error: #<Gem::LoadError: Unable to activate vagrant-vsphere-0.5.1, because nokogiri-1.6.0 conflicts with nokogiri (= 1.5.10)>
From the README: The plugin forces use of Nokogiri 1.5.10 to prevent conflicts with older versions of system libraries, specifically zlib.
@agrauch What type of conflict is that? Would it be possible to solve any other way?
We were seeing errors when installing the plugin on an enterprise SUSE server. We believe the problem involved compiling nokogiri against the libxml2/zlib libraries included with Vagrant and linking or running with libxml2/zlib installed on the system. This same issue was reported by another user here: https://groups.google.com/forum/#!msg/vagrant-up/KprN9tQtT34/asJDFdfoDoYJ. Another vagrant plugin ran into a similar issue and solved it by locking the nokogiri version: https://github.com/pradels/vagrant-libvirt/pull/63.
Locking the nokogiri version solved the issue on SUSE machine and on our MacOS X development machines. Admittedly, I don't have other vagrant plugins installed that require nokogiri. Although I do have nokogiri 1.6.0 and 1.15.10 installed.
I'm not sure how to solve this one. Conditionally setting the version of nokogiri based on the system would be cool but I have no idea how to do this.
I ran into this same problem. Unsurprisingly I had vagrant-windows installed first and then installed vagrant-vsphere. Vagrant would fail to load the vagrant-vsphere plugin because of the newer Nokogiri version. However I do have a hacky workaround
If you install vagrant-vsphere first it will install nokogiri 1.5.10. Other gems will see this version and not bother upgrading it. This worked both on my Mac and Ubuntu 12.04. Everyone wins.
That being said I'd rather change vagrant-vsphere gemspec to not require the older version of Nokogiri.
+1 for @sneal workaround. I uninstalled/reinstalled my plugins starting with vagrant-vsphere and was able to get it working. Thanks!
The vsphere plugin doesn't work on my system due to a conflict with another version of nokogiri already installed as a dependency of another vagrant plugin:
Setup:
Here are all the references to nokogiri in the gemspec files of my locally installed plugins or its dependencies:
Can you make a new release of the plugin that sets a minimum version of nokogiri instead of locking it to 1.5.10?