I assume this is something to do with gem hosting moving to github or something…I haven’t really been following ruby for a year or so so I’m not sure exactly what’s going on.just go in, locate the bin-directory and start update_rubygems from there. look into your path-variables and make sure everything is working correctly.otherwise you'll be back here very soon with an other issue. gem uninstall rubygems-update And I have found a similar problem here: But unfortunately no new solution....If you use a custom Ruby Gems server over SSL, this release will cause Ruby Gems to no longer connect unless your SSL cert is globally valid.You can configure SSL certificate usage in Ruby Gems through the :ssl_ca_cert and :ssl_verify_mode options in ~/.gemrc and /etc/gemrc.if not check your gem-directory which can be found by running gem environment for me it is "/usr/lib/ruby/gems/1.8/gems/rubygems-update-1.3.1/bin/ update_rubygems"Ah, I guess the problem is in the paths!I have changed the standard "gem" command to work by default with Passenger. Here is an output of your commands: $ gem list -l ... $ gem environment Ruby Gems Environment: - RUBYGEMS VERSION: 1.2.0 - RUBY VERSION: 1.8.6 (2008-08-08 patchlevel 286) [i686-linux] - INSTALLATION DIRECTORY: /opt/ruby-enterprise-1.8.6-20080810/lib/ ruby/gems/1.8 - RUBY EXECUTABLE: /opt/ruby-enterprise-1.8.6-20080810/bin/ruby - EXECUTABLE DIRECTORY: /opt/ruby-enterprise-1.8.6-20080810/bin - RUBYGEMS PLATFORMS: - ruby - x86-linux - GEM PATHS: - /opt/ruby-enterprise-1.8.6-20080810/lib/ruby/gems/1.8 - GEM CONFIGURATION: - :update_sources = you should find the rubygems-update gem there.
If you are using bundler be sure to install a 1.3.0.prerelease version or newer.), RSpec 2.99 gives you a detailed upgrade checklist tailored to your project.In addition, Yuji Nakayama has created Transpec – an absolutely amazing tool that can automatically upgrade most RSpec suites.is responsible not only for changing Ruby versions, but for installing rubies and managing gemsets, as well.
Breaking these responsibilities apart and selecting a tool for each job is a good alternative to using RVM.This process can be quite time consumming: you need to check on the internet for every updated gems, find where their changelog is hosted, and probably link to it in your commit message so that other developers will have a chance to review it too. All you have to do is to copy paste the output to the commit message, and you're done!