On Thu, Jul 29, 2010 at 12:46 PM, Dis Tec <[email protected]> wrote: > Version hell...I have the latest version of gems installed and gems -v > proves this, but somewhere an old copy is hanging about - how do I get > rid of this old version? This is driving me nuts! > > > > I seem to be getting conflicted installations of gems: > > For example > > $ ruby script/generate model product > Rails requires RubyGems >= 1.3.2 (you have 1.2.0). Please `gem update > --system` and try again. > > br...@ubuntu:~/RoR/Apps/OpenBenefit/depot$ gem update --system > ERROR: While executing gem ... (RuntimeError) > gem update --system is disabled on Debian. RubyGems can be updated > using the official Debian repositories by aptitude or apt-get. > > > > > br...@ubuntu:~/RoR/Apps/OpenBenefit/depot$ gem -v > 1.3.5 The weird thing is gem -v showing 1.3.5 However, you can try this on a Debian(-like) environment: sudo gem install rubygems-update #( 1.3.7 should be the latest version) sudo update_rubygems #if this doesn't work, try finding the right executable file in your gems path.
That would update your rubygems version. Hope it helps. -- Leonardo Mateo. There's no place like ~ -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
