When gem update --system goes wrong

When updating my colleague's ruby environment, I ran into the same issue I encountered on my own laptop a few months before. I couldn't find the solution right away, so I figured this could use some more google-love;

If for whatever reason, you need to update rubygems, and you get feedback like this;

sudo gem update --system
Updating RubyGems
Nothing to update

It means you are on one of the rubygems versions for which the update system got broken. You may or may not have installed the rubygems-update gem before. Running these lines should get you up and running again:

sudo gem install rubygems-update
sudo update_rubygems

Have something to add?



  • (required, but not displayed)

  • (optional)

About this article

You’re reading an entry titled “When gem update --system goes wrong”. Written

undefined tag `time_ago_in_words'
ago (03/05/2009) — and archived under ruby, rubygems, shell. So far, 0 people (dis)agreed with me, what do you think?

What the fuzz is all about

  1. 2 pages are tagged with WYM
  2. 1 page is tagged with absolute-urls
  3. 1 page is tagged with arrrrcamp
  4. 2 pages are tagged with documentation
  5. 2 pages are tagged with editor
  6. 2 pages are tagged with extension
  7. 2 pages are tagged with extensions
  8. 1 page is tagged with minitorial
  9. 1 page is tagged with navigation
  10. 10 pages are tagged with radiant
  11. 4 pages are tagged with rails
  12. 2 pages are tagged with ruby
  13. 2 pages are tagged with shell
  14. 1 page is tagged with sifr
  15. 2 pages are tagged with troubleshooting

Github activity

More places where you can find me

Back to top