gherkin-dependency incompatibility with vagrant

[tomaszdurka]

veewee-0.3.7 depends on cucumber >=1.0.0
cucumber-1.2.1 depends on gherkin ~> 2.11.0
gherkin-2.11.6 depends on json >= 1.7.6

BUT

vagrant-1.0.6 depends on json ~> 1.5.1

[dragonfax]

I've got this as an issue as well. It breaks not only veewee, but vagrant completely.

little-boobop:~ dragonfax$ vagrant
/Users/dragonfax/.rvm/rubies/ruby-1.9.3-p362/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:1637:in `raise_if_conflicts': Unable to activate gherkin-2.11.6, because json-1.5.1 conflicts with json (>= 1.7.6) (Gem::LoadError)

[jedi4ever]

@tomasdurka @dragonfax - I hear you ... you can try to use veewee standalone for now instead of through vagrant. (workaround)

I guess this gherkin - json - vagrant - fog - chef version dance comes up more often now . The right answer is probably to remove the gherkin/cucumber dependency completely and use simple script execution and check exit code .

[Xylakant]

I think the better way would be to get rid of the vagrant dependency. Vagrant will sooner or later not be installable as gem, so relying on it in the gemfile is not helpful. I actually consider the integration of veewee as vagrant plugin as not very essential - it just doesn't matter if I call vagrant basebox build oder veewee vbox build.

[jedi4ever]

@Xylakant - Good point - we can make the vagrant gem optional -
@mitchellh what do you think about that?

[prep]

As a temp solution, what worked for me was:

gem install json -v 1.5.4 --no-rdoc --no-ri
gem install gherkin -v 2.11.5 --no-rdoc --no-ri
gem install veewee --no-rdoc --no-ri

[petecheslock]

Awesome - that did the trick for me in the meantime.

[btoone]

Vendoring the gems also works in the meantime

bundle install --path vendor

Be sure to use bundle exec when using a vagrant command to use the vendored version

bundle exec vagrant basebox templates

[kevinburke]

this is still breaking - is there a fix that won't break everyone's environments?

[njam]

Using gherkin <= "2.11.5" should work.
So for me uninstalling the "2.11.6" works: gem uninstall gherkin -v 2.11.6

[mstanislav]

I went with the following and all is well for me.

gem uninstall gherkin -v 2.11.6
gem install gherkin -v 2.11.5 --no-rdoc --no-ri

[jedi4ever]

I'm pretty close to removing the gherkin dependency . Give me another day or so.

[MattGronwald]

In addition to the workarounds above I had to install missing xslt libs to make it work

sudo apt-get install libxslt-dev libxml2-dev

[jedi4ever]

Bye bye cucumber - 86bdd78

[nickchappell]

I tried @prep's steps but didn't have any luck. I'm actually using rbenv instead of RVM, if that makes any difference.

[jedi4ever]

@nickchappell can you try the latest git version ? I've removed the gherkin dependency completely in the new version

[dexterous]

Has this been released? Am still facing this issue with 0.3.7

[nickchappell]

@jedi4ever Is there a way to get the git version of Veewee to play with Vagrant installed via gems? Or is the git version of veewee intended to be installed and run with bundler, keeping it's own copy of the Vagrant gem in the folder you clone the veewee repo to? FWIW, I read (can't remember where) that Vagrant 1.0.7 would take care of the json gem dependency, but I don't know when that will be released.

[jedi4ever]

take the git version , run rake build , this will generate a gem file. that you can probably use for vagrant install

On 06 Mar 2013, at 18:45, nickchappell notifications@github.com wrote:

@jedi4ever Is there a way to get the git version of Veewee to play with Vagrant installed via gems? Or is the git version of veewee intended to be installed and run with bundler, keeping it's own copy of the Vagrant gem in the folder you clone the veewee repo to? FWIW, I read (can't remember where) that Vagrant 1.0.7 would take care of the json gem dependency, but I don't know when that will be released.

—
Reply to this email directly or view it on GitHub.

[nickchappell]

@jedi4ever Cool, I'll try it out when I get home from work. Thanks!

[nickchappell]

@jedi4ever Still had issues, but they were different, with Vagrant's gem dependency specifications. Changed the ~> to >= for net-ssh and net-scp in Vagrant's gemspec file. Things seem to function normally now.

[hcguersoy]

Hi folks,

have same issues here - conflicts due to dependencies in fog with net-scp. I fall back to fog 1.8 - this solved them.