rubygems1.8 package out of date
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libgems-ruby (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Jaunty |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: rubygems1.8
On ubuntu 8.10, most updated version of rubygems1.8 in repository:
rubygems1.8:
Installed: 1.3.0~RC1really
Candidate: 1.3.0~RC1really
Version table:
*** 1.3.0~RC1really
500 http://
100 /var/lib/
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://
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.
Changed in libgems-ruby: | |
status: | New → Confirmed |
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!