I went with option 1 of the below and we now have the RC candidate of chef loaded and presumably in use. However we have a strange problem that vagrant says the plugin is installed yet then fails to load it during vagrant up. The relevant section is here:
ERROR root: Failed to load plugin: vagrant-librarian-chef ERROR root: -- Error: # ERROR root: -- Backtrace: ERROR root: c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:2007:in raise_if_conflicts' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:1176:inactivate' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:1212:in block in activate_dependencies' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:1198:ineach' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:1198:in activate_dependencies' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:1180:inactivate' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:1212:in block in activate_dependencies' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:1198:ineach' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:1198:in activate_dependencies' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:1180:inactivate' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems.rb:186:in rescue in try_activate' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems.rb:183:intry_activate' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:117:in rescue in require' c:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:124:inrequire' c:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant.rb:204:in require_plugin' c:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/environment.rb:760:inblock in load_plugins' c:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/environment.rb:751:in each' c:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/environment.rb:751:inload_plugins' c:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/environment.rb:132:in initialize' c:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.3/bin/vagrant:105:innew' c:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.3/bin/vagrant:105:in <top (required)>' c:/HashiCorp/Vagrant/bin/../embedded/gems/bin/vagrant:23:inload' c:/HashiCorp/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `' INFO interface: error: Failed to load the "vagrant-librarian-chef" plugin. View logs for more details. On Monday, February 3, 2014 1:05:51 PM UTC+1, Rhys Gareth wrote: > > 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]> 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]. >>> 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.
