[Bug 302990] [NEW] rubygems1.8 package out of date

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Luca Falavigna (dktrkranz):

Binary package hint: rubygems1.8

On ubuntu 8.10, most updated version of rubygems1.8 in repository:
rubygems1.8:
  Installed: 1.3.0~RC1really1.2.0-2ubuntu3
  Candidate: 1.3.0~RC1really1.2.0-2ubuntu3
  Version table:
 *** 1.3.0~RC1really1.2.0-2ubuntu3 0
        500 http://us.archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

This package is out-of-date for the new version of Ruby on Rails, 2.2 as this version of Rails requires 1.3.1. Because 1.2.0 is the latest apt-get repository version, users must use `gem update --system` to upgrade RubyGems. Since this functionality is disabled:
`sudo gem update --system`
ERROR:  While executing gem ... (RuntimeError)
    gem update --system is disabled on Debian. RubyGems can be updated using the official Debian repositories by aptitude or apt-get.

The user must then do a manual installation of the gem system with `sudo
gem install rubygems-update` and `sudo update_rubygems`. This and other
alternative processes are outlined in a blog post by "Sam Ruby" at
http://intertwingly.net/blog/2008/11/23/RubyGems-1-3-1-on-Ubuntu-8-10.

What is the danger of leaving the --system option open? I am unfamiliar
with the process of migrating a new version of anything to the
repository, but I believe it should be left unlocked unless the packages
will be updated in a timely fashion.

** Affects: libgems-ruby (Ubuntu)
     Importance: Wishlist
         Status: Confirmed

** Affects: libgems-ruby (Ubuntu Jaunty)
     Importance: Wishlist
         Status: Confirmed

-- 
rubygems1.8 package out of date
https://bugs.edge.launchpad.net/bugs/302990
You received this bug notification because you are a member of Ubuntu Sponsors for universe, which is a direct subscriber.