Hello everyone,
I’m novice in linux, ruby and rails. I’ve reinstalled my ubuntu
operative system, the ruby module, and also the rubygems module. After
that I’ve updated rubygems by this command:
sudo gem update --system
Ruby gem was updated successfully, but now I can’t use ruby gem, each
time I write:
sudo gem list -r
or:
sudo gem help commands
or something else, I get the follow answer:
/usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)
I don’t know what it means, so, does someone know the meaning? and does
someone know how I can fix it?
Thank you very much.
Manuel Montañés wrote:
/usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)
This normally suggests the update didn’t update your “gem” command, or
else updated one in a different area (perhaps you now have more than one
version of the command installed?).
The gem command is a Ruby script and should have the 2 lines:
require ‘rubygems’
require ‘rubygems/gem_runner’
I suspect you are missing the 2nd line…
On Tue, 11 Mar 2008 09:21:50 -0500, Manuel Montañés wrote:
I don’t know what it means, so, does someone know the meaning? and does
someone know how I can fix it?
Thank you very much.
You should ideally be unable to run gem update --system on Debian and
Ubuntu. This was discussed here on ruby talk, and also in a Debian bug
at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452547. I wouldn’t know
whether this change has propagated to ubuntu yet, but you shouldn’t run
“gem update --system” when the system package manager is in charge of
which rubygems version is installed on your system.
To fix this, apt-get install --reinstall rubygems, and get rid of any
rubygems stuff you may find in /usr/local
–Ken
Ken B. wrote:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452547. I wouldn’t know
whether this change has propagated to ubuntu yet, but you shouldn’t run
“gem update --system” when the system package manager is in charge of
which rubygems version is installed on your system.
To fix this, apt-get install --reinstall rubygems, and get rid of any
rubygems stuff you may find in /usr/local
–Ken
Ken, thanks. I’ve posted this problem twice to this list and gotten
nothing, and this morning you give me…well not me exactly…the
answer. I assumed that when you said
"
To fix this, apt-get install --reinstall rubygems, and get rid of any
rubygems stuff you may find in /usr/local
"
you got that backwards. In any case, I removed the rubygems stuff in
/usr/local and THEN did the reinstall. Now for the first time in 4 days
I have working rubygems. Man…this needs to be written down somewhere.
Like in my notes. So shall it be.
Thanks again.
Tom
–
Tom C., MS MA, LMHC
Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website & psychotherapy weblog)
<< sleightmind.wordpress.com >> (mental health issues weblog)
<< directpathdesign.com >> (web site design & consultation)
On Tue, 11 Mar 2008 13:01:53 -0500, Tom C. wrote:
sudo gem update --system
or something else, I get the follow answer:
Ubuntu. This was discussed here on ruby talk, and also in a Debian bug
/usr/local and THEN did the reinstall. Now for the first time in 4 days
I have working rubygems. Man…this needs to be written down somewhere.
Like in my notes. So shall it be.
That order’s fine too. I figure it could be done in either order.
–Ken