Ruby version >=2 Required [#2745239]

==> default: [2016-06-08T20:40:55+00:00] ERROR: Exception handlers complete
==> default: [2016-06-08T20:40:55+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> default: Chef Client failed. 94 resources updated in 412.459496146 seconds
==> default: [2016-06-08T20:40:55+00:00] ERROR: gem_package[mailcatcher] (vdd::mailcatcher line 5) had an error: Gem::InstallError: mime-types-data requires Ruby version >= 2.0.
==> default: [2016-06-08T20:40:55+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

I'm getting this error when trying to Vagrant up. I'm currently running Vagrant on Mac:
Vagrant 1.8.1
VirtualBox 4.3.16

I tried changing a line in the initial.sh file from:
apt-get install build-essential ruby1.9.1-dev --no-upgrade --yes &> /dev/null
to:
apt-get install -y build-essential ruby2.0 ruby2.0-dev ruby2.0-doc &> /dev/null
with no luck.

Comment	File	Size	Author
#4	ruby2.2-2745239-4.patch	866 bytes	ericjenkins

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

8 June 2016 at 21:11

hook_awesome created an issue. See original summary.

Comment #2

adam_ CreditAttribution: adam_ as a volunteer commented 8 June 2016 at 21:12

Issue summary:

View changes

Comment #3

ericjenkins CreditAttribution: ericjenkins at Exel Digital for Promet Source commented 8 July 2016 at 21:46

When I run vagrant up, I also see the message you refer to. Here's a snippet of my computer's output:

==> default: Setting up ruby1.9.1-dev (1.9.3.484-2ubuntu1.2) ...
==> default: Updating certificates in /etc/ssl/certs... 
==> default: 0 added, 0 removed; done.
==> default: Running hooks in /etc/ca-certificates/update.d....
==> default: done.
==> default: Building native extensions.  This could take a while...
==> default: Building native extensions.  This could take a while...
==> default: Building native extensions.  This could take a while...
==> default: Building native extensions.  This could take a while...
==> default: Building native extensions.  This could take a while...
==> default: ERROR:  Error installing chef:
==> default:    rack requires Ruby version >= 2.2.2.
==> default: installed ruby and chef
==> default: Running provisioner: chef_solo...
    default: Installing Chef (latest)...
==> default: Generating chef JSON and uploading...
==> default: Running chef-solo...

The ruby error occurs right before chef provisioning begins. However, despite seeing this message, Chef provisioning proceeds as usual, and my box still provisions correctly and successfully.

@hook_awesome: Does your box also provision successfully? Is this error worth fixing?

Comment #4

ericjenkins CreditAttribution: ericjenkins at Exel Digital for Promet Source commented 10 July 2016 at 19:01

File	Size
ruby2.2-2745239-4.patch	866 bytes

I came up with a patch to update Ruby to version 2.2. See attached Patch #4.

Not only does Patch #4 fix the Ruby error referenced in this ticket for me, but it also appears to solve the Mailcatcher error reported in Issue 2697107.

I hope this patch works for others, too!

Comment #5

Johnnie Walker CreditAttribution: Johnnie Walker as a volunteer commented 11 August 2016 at 22:36

Thanks for this.

I submitted the Mailcatcher Issue.

Which version of VDD did you run this patch against? Was it 8.x-1.0-alpha4 or 8.x-1.x-dev ?

Comment #6

ericjenkins CreditAttribution: ericjenkins at Exel Digital for Promet Source commented 11 August 2016 at 22:55

My apologies, @Johnnie Walker. I ran Patch #4 against the 8.x-1.x-dev version of VDD.

Comment #7

sheldonkreger CreditAttribution: sheldonkreger commented 13 August 2016 at 20:27

My build was failing until I applied this patch. Thank you.

Comment #8

laurelstreng CreditAttribution: laurelstreng commented 19 August 2016 at 14:04

Thanks so much! So many errors until I applied patch #4

Comment #9

LiamPower CreditAttribution: LiamPower commented 20 August 2016 at 15:06

Status:

Active

» Needs review

This is exactly the same as what I did with my customised VDD.

Comment #10

awm CreditAttribution: awm commented 3 January 2017 at 17:21

Does it make sense to install 2.3 instead?

Comment #11

LiamPower CreditAttribution: LiamPower commented 22 January 2017 at 12:49

I would suggest just getting this added in to make the the current VM work. I'm going to download the dev VM and apply the patch shortly to make sure it does work so we can RTBC this.

Comment #12

LiamPower CreditAttribution: LiamPower commented 22 January 2017 at 16:28

Status:

Needs review

» Reviewed & tested by the community

With this patch and patch #2 from https://www.drupal.org/node/2789071 this works. RTBC - Hopefully someone will merge these in, I'm, looking at @awm as he recently became a co-maintainer.

Comment #13

LiamPower CreditAttribution: LiamPower commented 22 January 2017 at 18:16

Comment #14

25 January 2017 at 18:40

awm committed 313f157 on 8.x-1.x authored by ericjenkins

Issue #2745239 by ericjenkins, hook_awsome, LiamPower, awm: Ruby version...

Comment #15

awm CreditAttribution: awm commented 25 January 2017 at 18:44

Status:

Reviewed & tested by the community

» Fixed

commited & pushed to 8.x-1.x
Also, I don't see how this is related to the drush master issue. I am removing the link between the 2 issues. @liam please re-add if you are convinced they're related.