[hardy] gem update --system breaks rubygems

Bug #206596 reported by Jon Leighton
Affects Status Importance Assigned to Milestone
libgems-ruby (Debian)
Fix Released
libgems-ruby (Ubuntu)
Fix Released

Bug Description

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

That's it really...

Revision history for this message
danieroux (accounts+launchpad-danieroux) wrote :
Revision history for this message
Neil Wilson (neil-aldur) wrote :

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

Changed in libgems-ruby:
status: New → Confirmed
Revision history for this message
Mike Trim (miketrim) wrote :

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


Revision history for this message
Bryan McLellan (btm) wrote :

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

Changed in libgems-ruby:
status: Unknown → Fix Released
Revision history for this message
Simon Huerlimann (huerlisi) wrote :

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'.

Changed in libgems-ruby (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.