jedi4ever / veewee

Easing the building of vagrant boxes
MIT License
4.29k stars 779 forks source link

ohai requires Ruby version >= 2.0.0. #1025

Open boldandbusted opened 9 years ago

boldandbusted commented 9 years ago

I forked your repo to add Debian 7.8 support. I merely changed references in the config replacing 7.7 with 7.8. Everything seems to go swimmingly until...

veewee vbox build 'debian-7-dot-8' --workdir=/dev/shm/vagrant --force

[..giant snip..] Executing command: echo 'vagrant'|sudo -S bash './chef.sh' Fetching: mixlib-config-2.1.0.gem (100%) Fetching: mixlib-cli-1.5.0.gem (100%) Fetching: mixlib-log-1.6.0.gem (100%) Fetching: mixlib-authentication-1.3.0.gem (100%) Fetching: mixlib-shellout-2.0.1.gem (100%) Fetching: mime-types-1.25.1.gem (100%) Fetching: systemu-2.6.4.gem (100%) Fetching: ffi-1.9.6.gem (100%) Building native extensions. This could take a while... Fetching: libyajl2-1.2.0.gem (100%) Building native extensions. This could take a while... Fetching: ffi-yajl-1.3.1.gem (100%) Building native extensions. This could take a while... Fetching: net-dhcp-1.3.2.gem (100%) Fetching: ipaddress-0.8.0.gem (100%) Fetching: wmi-lite-1.0.0.gem (100%) Fetching: rake-10.4.2.gem (100%) Fetching: ohai-8.0.1.gem (100%) ERROR: Error installing chef: ohai requires Ruby version >= 2.0.0. ERROR: exit code 1

If you need more info, please ask! :)

boldandbusted commented 9 years ago

Oh, hrm, might this be a conflict with puppet's deps? Just a guess.

mpapis commented 9 years ago

can you gist it all?

boldandbusted commented 9 years ago

https://gist.github.com/boldandbusted/08ce17a7146108b59861#file-veewee-debian-7-8

Thanks!

mpapis commented 9 years ago

I would bet it has to do with https://github.com/jedi4ever/veewee/blob/master/templates/Debian-7.7.0-amd64-netboot/ruby.sh :

ohai requires Ruby version >= 2.0.0.

and as much I can find Debian 7 comes with ruby 1.8 and 1.9 you would need to:

rubo77 commented 9 years ago

You can install Ruby 2.0 via my script at stackoverflow.com/questions/16222738/-/29584352#29584352

I had the same problem, but it solved without installing ruby2. I don't know exactly how, but what I did was:

Now everything runs through fine, maybe it helps

mpapis commented 9 years ago

@rubo77 make sure to open a pull request with a fix ... if you did not do it yet ;)

rubo77 commented 9 years ago

@mpapis you can do it, I don't use veewee, just came by here with a similar problem in another project and shared my result with you

have fun!

mpapis commented 9 years ago

thanks, I'm only janitor here, anyone interested in playing with it and applying the fix in pull request