[hardy] gem update --system breaks rubygems

[Jon Leighton]

$ gem
/usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)

That's it really...

[danieroux (accounts+launchpad-danieroux)]

I can confirm that the same happens to me (and Sam Ruby http://intertwingly.net/blog/2008/03/21/Hardy-Heron-Beta-on-T61P).

Fix is here: http://www.nickpeters.net/2007/12/31/fix-for-uninitialized-constant-gemgemrunner-nameerror

[Neil Wilson (neil-aldur)]

You should be using apt to update rubygems, not the gem command.

[Mike Trim (miketrim)]

Unfortunately, using apt to update rubygems doesn't work if the rubygems package in the repositories doesn't get updated.

#302990

[Bryan McLellan (btm)]

This was fixed in debian in v1.0.0-1, "fix" being that 'gem update --system' was disabled. Short of a package making it way into hardy-updates (since hardy is LTS, but this bug alone probably isn't enough to justify an update.), you can get v1.1.1-1~hardy1 from hardy-backports [1].

[1] http://packages.ubuntu.com/hardy-backports/rubygems

[Simon Huerlimann (huerlisi)]

As this has been fixed in Lucid as the new LTS and will never been available through hardy-updates anymore, I'm closing this bug by marking it as 'Fix Released'.