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
--
[hardy] gem update --system breaks rubygems
https://b
** Changed in: libgems-ruby (Debian)
Status: Unknown => Fix Released
--
[hardy] gem update --system breaks rubygems
https://bugs.launchpad.net/bugs/206596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
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://pac
** Bug watch added: Debian Bug tracker #452547
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452547
** Also affects: libgems-ruby (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452547
Importance: Unknown
Status: Unknown
--
[hardy] gem update --system breaks ruby
Unfortunately, using apt to update rubygems doesn't work if the rubygems
package in the repositories doesn't get updated.
#302990
--
[hardy] gem update --system breaks rubygems
https://bugs.launchpad.net/bugs/206596
You received this bug notification because you are a member of Ubuntu
Bugs, whic
