RubyGems 1.0 Gem Runner Bug
Regarding the error uninitialized constant Gem::GemRunner, there was, apparently, a warning which I missed when I upgraded RubyGems which said:
NOTE: If you have installed RubyGems using a package manager you may want to install a new RubyGems through the same packaging system.
I asked about this at Eric Hodell's blog. The bottom line is that if you don't interpret this bland warning for the screeching banshee it should be, you'll run into the problems I had when upgrading my debian machine.
The lower-level something is, the more I subconsciously expect it should just work. For example, I think C mostly just works, and my BIOS is reliable to an even greater number of nines. I would be annoyed if I had to maintain, upgrade or pay attention to those things. In this case I didn't even "want" to upgrade RubyGems-I got stuck doing it while fixing some other chain of dependencies when upgrading to rails 2.0 and I didn't give it special care and feeding because I couldn't imagine something so basic as a ruby component upgrade on a common platform like Debian as likely to cause harm. Woops.
If you're arriving here after searching for the GemRunner error (more than 20 people so far) here's a link to my hack:
uninitialized constant Gem::GemRunner with RubyGems 1.0
RubyGems 1.0 announcement on Eric Hodell's blog
NOTE: If you have installed RubyGems using a package manager you may want to install a new RubyGems through the same packaging system.
I asked about this at Eric Hodell's blog. The bottom line is that if you don't interpret this bland warning for the screeching banshee it should be, you'll run into the problems I had when upgrading my debian machine.
The lower-level something is, the more I subconsciously expect it should just work. For example, I think C mostly just works, and my BIOS is reliable to an even greater number of nines. I would be annoyed if I had to maintain, upgrade or pay attention to those things. In this case I didn't even "want" to upgrade RubyGems-I got stuck doing it while fixing some other chain of dependencies when upgrading to rails 2.0 and I didn't give it special care and feeding because I couldn't imagine something so basic as a ruby component upgrade on a common platform like Debian as likely to cause harm. Woops.
If you're arriving here after searching for the GemRunner error (more than 20 people so far) here's a link to my hack:
uninitialized constant Gem::GemRunner with RubyGems 1.0
RubyGems 1.0 announcement on Eric Hodell's blog
3 comments
Comments
-
FYI, your link is to edit the article.
-
Woops! Thanks Justin!
-
Thanks for posting this! - quite obscure... I had upgraded rails and rubygems on another machine without a problem. On a second one, it gave this error, after the upgrade - 'upgrade rubygems-update' (I installed rubygems on ubuntu 'by hand', not though the ubuntu package manager...).