RubyGems 1.5.0 Released: Now Supports Ruby 1.9.2
Ryan Davis has announced the release of RubyGems 1.5.0. It comes just a month after the release of 1.4 which, notoriously, didn't work with Ruby 1.9.2. These problems have now all been ironed out and Ruby 1.8 and 1.9 users alike can safely upgrade (fingers crossed).
RubyGems is the popular (and official - as of Ruby 1.9) Ruby package manager with which most significant Ruby libraries and tools are distributed. The 1.5 release sees it pick up a few bug fixes and some enhancements, including:
- Ruby 1.9 support
- Post-build hooks that can cancel the gem install
Gem.find_filesis now 40% faster (on Ruby 1.9)- Better errors for corrupt Gem files, including paths
- A new UPGRADING documentation file to help with Ruby 1.9-related issues
gem updateno longer erroneously tries to update RubyGems itself by default
To upgrade to RubyGems 1.5.0, run:
gem update --systemAlternatively, you can learn more in the new UPGRADING documentation, or if you don't already have RubyGems for some reason, you can download it from RubyGems.org.
UPDATE: RubyGems 1.5.0 and Bundler are not the best of friends! If you're depending on Bundler tonight, don't install RubyGems 1.5.0 just yet. However, a 1.5 compatible version of Bundler is due within the next 24 hours. A new version of Bundler has been released, supporting RubyGems 1.5.0. Upgrade now :-)
February 1, 2011 at 2:54 am
Rubygems 1.5 with ruby 1.9.2p136 on osX renders the following error when I try to 'bundle install' on my rails app:
/gems/bundler-1.0.9/lib/bundler/ui.rb:56:in `': uninitialized constant Gem::SilentUI (NameError)
February 1, 2011 at 3:26 am
Thanks for the rubygems update. Unfortunately, after updating - bundler shows this error:
uninitialized constant Gem::SilentUI (NameError)
any thoughts?
February 1, 2011 at 3:28 am
Except bundler is currently broken...
February 1, 2011 at 4:55 am
Unfortunately the 1.5 release makes breaking changes for Bundler. We'll try to release Bundler 1.0.10 with 1.5 compatability as soon as we possibly can -- hopefully February 1st.
February 1, 2011 at 5:50 am
If you use bundler (and who doesn't) be careful! This update seems to break things:
/gems/bundler-1.0.9/lib/bundler/ui.rb:56:in `': uninitialized constant Gem::SilentUI (NameError)
Any links on how to revert back to 1.3?
February 1, 2011 at 5:57 am
I'm pretty sure it's Ryan Davis, not Eric. Good news thought, waiting for bundler compatibility now :)
February 1, 2011 at 6:14 am
Apologies to Ryan Davis - now fixed. Thanks JBB!
Also, thanks for the Bundler reports. This has now been confirmed and I've just seen this on IRC:
No worries, I tracked it down and it's a Bundler thing. I fixed a couple things and submitted a PR but they say they're gonna be working on getting a full 1.5 compatible fix in by tomorrow.
I also saw this on Twitter:
I guess it's only fair that rubygems would break bundler after all the damage bundler has done to rubygems
February 1, 2011 at 6:27 am
@Kevin: I don't know if you're running RVM, but I've just found that
rvm rubygems 1.3.7reverted it OK for me (and Bundler now works). It does come up with an error when you run that command but the downgrade itself seems to work (enough for Bundler to install new things and my specs to all run at least..)February 1, 2011 at 7:35 am
How can they release this if it breaks Bundler? Someone must have noticed that. I thought Ruby was a community..
February 1, 2011 at 4:04 pm
@Martijn: Bundler is a related, but not under-control project.
@everyone:
I believe the new release of bundler -released just now- fixes the issues, as stated in the changelog. I'm about to test it.
https://github.com/carlhuda/bundler/blob/1-0-stable/CHANGELOG.md
Comments welcome. I'll get back to you guys.
February 21, 2011 at 2:42 pm
Unfortunately it is still a little buggy