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