Mitchell, thank you! Sorry, I'm not familiar with ruby/gems, so this has required some learning. I hope I can solve it in the next step/answer from you:
vagrant-librarian-chef depends up librarian-chef, which depends on chef, which has the ffi dependency problem. This has just been fixed in a release candidate version of Chef, now referenced on rubygems.org (http://rubygems.org/gems/chef) What is the best/cleanest way to uninstall/reinstall to get this fix? I am guessing there are two alternatives: 1. Manually install the RC gem version of chef first, then run "vagrant plugin install vagrant-librarian-chef" and librarian-chef should use whatever chef version I have cached, i.e. the latest RC one. 2. Manually edit the .gemspec of librarian.chef to add dependency for the RC version of Chef, and let it automatically download that locally Thanks again, Rhys On Monday, February 3, 2014 11:54:24 AM UTC+1, Mitchell Hashimoto wrote: > > Rhys, > > Since this is a bug with the gemspec of the plugin, you'd have to actually > go into the "~.vagrant.d/gems/gems" folder, find the gem that depends on > the wrong FFI version, and change it in that gemspec itself. > > Best, > Mitchell > > > On Mon, Feb 3, 2014 at 11:52 AM, Rhys Gareth <[email protected]<javascript:> > > wrote: > >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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.
