uninitialized constant Gem::GemRunner

written by Eric on December 20th, 2007 @ 02:15 PM

On my Debian machine I upgraded rubygems this morning. Suddenly gem -v wouldn't work and threw uninitialized constant Gem::GemRunner. Thinking the install was half-baked, I uninstalled, reinstalled, using apt-get. Kept getting v1.0 of RubyGems and the same error. Gave up and used nano to toss the line below into /usr/bin/gem

require 'rubygems/gem_runner'

Haven't seen anyone else complaining so far, which is really the only strange part. Works for me now, though. Very annoying to have to hack a system library to get it to work, though--makes me feel dirty. I'll be looking for a better answer. :-)

posted in:

tags:

#

comments are closed


6 comments

Comments

  • Matthew on 25 Dec 23:15

    FYI, I ran into exactly the same problem... your hack worked for me too. Thanks!

  • Troy on 26 Dec 11:47

    had the same problem and fix worked, thanks. I also did the same upgrade on Fedora 8 and had no problems.

  • Eric on 27 Dec 10:05

    Cool! Glad to see it was useful to other people. I added another post with a little more about the error. On my to-do list is to see what this file looks like in the source and see if this require is the only difference in 1.0.

  • Philip Ratzsch on 27 Dec 11:11

    Thanks for posting this Eric - I'm new to Ruby and this saved me a lot of time.

  • Michael Flanagan on 27 Dec 20:57

    Thanks, I needed this fix too.

  • Justin on 04 Jan 10:34

    I had installed gem via the package manager, then overwrote it with a downloaded version, and *still* had this problem. Thanks for this.

Comments are closed