We have a Vagrant-based project which is working fine on OS X and Linux but 
failing on Windows. The culprit is the vagrant-librarian-chef plugin. It 
installs without error, but causes "vagrant up" to fail:

 INFO environment: Loading plugin from JSON: vagrant-librarian-chef
ERROR root: Failed to load plugin: vagrant-librarian-chef
ERROR root:  -- Error: #<Gem::LoadError: Unable to activate 
chef-11.8.2-x86-ming
w32, because ffi-1.9.3-x86-mingw32 conflicts with ffi (= 1.3.1)>

The root cause appears to have been fixed here: 
https://tickets.opscode.com/browse/CHEF-4913 but this has not flowed 
through to the Vagrant plugin.

I'd try to patch this locally myself but I'm confused by how the vagrant 
plugin namespace works and how I would do this? e.g. could I fork the 
plugin, update it, build it and copy it to a local path for vagrant plugin 
install to use, rather than it pulling the old/unworking version from the 
web?

Rhys

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to