Posted over 7 years ago. Visible to the public.

rbenv: How to update list of available Ruby versions on Linux

When you tell rbenv to install a Ruby it does not know about, you will get an error message.

$ rbenv install 2.1.2 ruby-build: definition not found: 2.1.2 You can list all available versions with `rbenv install --list'. If the version you're looking for is not present, first try upgrading ruby-build. If it's still missing, open a request on the ruby-build issue tracker:

(Fun fact: Recent versions of ruby-build will give you a more helpful error message which just tells you the following.)

On Linux, you probably installed ruby-build as an rbenv plugin. Updating is easy:

git -C ~/.rbenv/plugins/ruby-build pull

Done. Rbenv will know about the new versions immediately.

Adding new Ruby versions to ruby-build

Since we are using a fork of ruby-build to work around some issues with old Rubies, our fork might not yet know about newly released Ruby versions.

If this is the case, it should usually only be necessary to merge the upstream ruby-build master branch into our local-openssl-for-old-rubies branch. If you cannot do this yourself, ask on Slack.

Flaky tests are tests that sometimes fail for no obvious reason. They are the plague of many end-to-end (E2E) test suites that automate the browser through tools like Capybara and Selenium.

Join our free training event and learn to fix any flaky test suite, even in large legacy applications.

Owner of this card:

Arne Hartherz
Last edit:
over 1 year ago
by Tobias Kraze
About this deck:
We are makandra and do test-driven, agile Ruby on Rails software development.
License for source code
Posted by Arne Hartherz to makandra dev
This website uses short-lived cookies to improve usability.
Accept or learn more