rubygems1.8 package out of date

[Jonte]

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.

[dstar (dstar-pele)]

It seems to me that if Ubuntu wishes to disable the --system option, it is critical that RubyGems be kept up to date. Either provide updates in a timely fashion (1.3.1 is almost two months old, and 1.3.0 is _three_ -- but the rubygems package provides a version of rubygems that's over six months old) or leave the --system option open. The current situation results in an unusable system for anyone who wishes to run Rails or Merb!

[Steve Guio (guioking-deactivatedaccount)]

The version 1.3.1-1 is now in Debian (experimental), please merge it.

[Nathan Handler (nhandler)]

What is the current status of this bug? Is anybody working on preparing a merge of version 1.3.1-1 from Debian's experimental repository?

[Bryan McLellan (btm)]

The problem with --system is that the package updates itself. This breaks the debian package [1]. If you then uninstalled or upgraded using the packaging system, unknown things would happen because it wouldn't know anything about what rubygems had done to itself. See also the current version of debian's policy on rubygems [2], which is in the process of having some revamping [3] done at the moment with the help of the ruby community.

You really should uninstall the debian package and install from source if you really want to use 'gem update --system'. Personally, I've built from the debian experimental source and maintain the package in a local repository.

The last time I spoke to the MOTU team on IRC a month ago about trying to get some ruby packages into Ubuntu, they expressed that they were heavily understaffed and with jaunty coming up didn't to maintain new packages. I'm getting the packages into Debian instead and we'll pick them up on the next sync I suppose. I did have an offer to pull them from NEW before jaunty ships but I'm doubtful that it will happen.

With that in mind and since we're past FeatureFreeze for Jaunty [4], it's pretty likely we won't get a new version of gems in 9.04. I agree this is hugely disappointing. Canonical/Ubuntu's promise of a regular release schedule is useless to us server folks who aren't getting any love. Build your own packages and maintain a local repository if you want to use Ubuntu as a server platform in the interim.

[1] https://bugs.launchpad.net/ubuntu/+source/libgems-ruby/+bug/206596
[2] http://pkg-ruby-extras.alioth.debian.org/rubygems.html
[3] http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2009-February/003382.html
[4] https://wiki.ubuntu.com/JauntyReleaseSchedule

[Scott Kitterman (kitterman)]

If someone will mind the packages, I don't mind giving an FFe for this.

[Bryan McLellan (btm)]

Scott,

If you or someone else from MOTU will sponsor any required patches, I will gladly support the gems package and other ruby packages for that matter.

[Scott Kitterman (kitterman)]

I'm using my Server Team delegate authority to approve this. Please use the normal sponsorship process to get this uploaded.

[Iain Lane (laney)]

I don't see anything to sponsor. Please resubscribe the sponsors team when ready (sooner rather than later; schedules are getting somewhat tight now).

[Bryan McLellan (btm)]

Bug 334065 is the bug for the package sync. I couldn't tell you what else needs to be done, I believe it's out of my hands not being an Ubuntu Developer/MOTU.

[Jamie Strandboge (jdstrand)]

This is now synced from Debian. See bug #334065.