Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rvm (and hence mailcatcher) installation broken (upstream bug) #1235

Merged
merged 1 commit into from
Jul 21, 2017

Conversation

kraftner
Copy link
Contributor

Expected Behavior

vagrant up installs rvm with a current ruby and then installs mailcatcher

Current Behavior

Due to an upstream bug in rvm (or better the installer) the installation of rvm somewhat fails, skipping the ruby installation, which then leads to mailcatcher failing to install with symptoms similar to #985

Possible Solution

This line

curl --silent -L "https://get.rvm.io" | sudo bash -s stable --ruby

could be replaced by

curl --silent -L "https://raw.githubusercontent.com/rvm/rvm/stable/binscripts/rvm-installer" | sudo bash -s stable --ruby

The reasoning for this is that https://get.rvm.io points to the master branch of rvm which might not play along with the stable version we're installing. Fix taken from the upstream issue.

I have applied the above fix and the provisioning worked flawlessly.

Steps to Reproduce (for bugs)

  1. vagrant up
  2. Watch the provisioning and look for this section
==> default: bash: line 880: __rvm_print_headline: command not found
==> default:  * Mailcatcher [not installed]
==> default: Building native extensions.  This could take a while...
==> default: ERROR:  Error installing mailcatcher:
==> default:    ERROR: Failed to build gem native extension.
==> default: 
==> default:         /usr/bin/ruby1.9.1 extconf.rb
==> default: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)
==> default:    from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
==> default:    from extconf.rb:2:in `<main>'
  1. e.g. run rvm list to check that ruby-2.4.0 is not installed

Your Environment

  • VVV version: 2.0.0 / master
  • Vagrant version: 1.7.2
  • VM Provider name: VirtualBox
  • VM Provider version: 4.3.36_Ubuntur105129
  • Operating System and version: Ubuntu 14.04

@jonathan-dejong
Copy link

Can confirm that this works.

@LoreleiAurora LoreleiAurora merged commit 36fd66c into Varying-Vagrant-Vagrants:develop Jul 21, 2017
@jeremyfelt jeremyfelt added this to the 2.0.1 milestone Sep 22, 2017
@jeremyfelt jeremyfelt modified the milestones: 2.0.1, 2.1 Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants