rvm (and hence mailcatcher) installation broken (upstream bug) #1235
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Expected Behavior
vagrant up
installs rvm with a current ruby and then installs mailcatcherCurrent 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
could be replaced by
The reasoning for this is that
https://get.rvm.io
points to themaster
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)
vagrant up
rvm list
to check thatruby-2.4.0
is not installedYour Environment