RubyGems 1.1.1

Eric Hodel | Fri, 11 Apr 2008 05:19:00 GMT

Posted in ,

Release 1.1.1 fixes some bugs.

Bugs Fixed:

  • Gem.prefix now returns non-nil only when RubyGems was installed outside sitelibdir or libdir.
  • The gem server gem list now correctly links to gem details.
  • gem update --system now passes --no-format-executable to setup.rb.
  • Gem::SourceIndex#refresh! now works with multiple gem repositories.
  • Downloaded gems now go into --install-dir's cache directory.
  • Various fixes to downloading gem metadata.
  • gem install --force now ignores network errors too.
  • gem pristine now rebuilds extensions.
  • gem update --system now works on virgin Apple ruby.
  • Gem::RemoteFetcher handles Errno::ECONNABORTED.
  • Printing of release notes fixed.

For a full list of changes to RubyGems including credits, see the ChangeLog file.

How can I get RubyGems?

NOTE: If you have installed RubyGems using a package system you may want to install a new RubyGems through the same packaging system.

If you have a recent version of RubyGems (0.8.5 or later), then all you need to do is: 

  $ gem update --system   (you might need to be admin/root)

(Note: You may have to run the command twice if you have any previosly installed rubygems-update gems).

If you have an older version of RubyGems installed, then you can still do it in two steps: 

  $ gem install rubygems-update  (again, might need to be admin/root)
  $ update_rubygems              (... here too)

If you don’t have any gems install, there is still the pre-gem approach to getting software … doing it manually:

  1. DOWNLOAD FROM: rubyforge.org/frs/?group_id=126
  2. UNPACK INTO A DIRECTORY AND CD THERE
  3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege)

To File Bugs

The RubyGems bug tracker can be found on RubyForge at: rubyforge.org/tracker/?func=add&group_id=126&atid=575

When filing a bug, gem env output will be helpful in diagnosing the issue.

If you find a bug where RubyGems crashes, please provide debug output. You can do that with gem --debug the_command.

Thanks

Keep those gems coming!

— Jim & Chad & Eric (for the RubyGems team)

6 comments

Comments RSS FEED

Seems pretty screwed up at the moment. I just updated to RubyGems 1.1.1 and it stalls on “Bulk updating Gem source index for: http://gems.rubyforge.org/”. Been sitting there for 15 minutes….

I guess I’ll give it another 5 min then I’m downgrading back to 1.1.0

tim said about 3 hours later

I went back to RubyGems 1.1.0 and now Bulk Source update started working again.

I think 1.1.1 screwed something up. I’m on Ubuntu 7.10

tim said about 3 hours later

None of the testing done by users on the RubyForge mailing list exhibited this problem. Can you run again with—debug, and if you can still reproduce file a bug per the instructions above?

Eric Hodel said about 4 hours later

I think RubyForge might be the issue. I am on Ubuntu 7.10 and gem update—system, wget, and Firefox all timeout on the yawl URL after receiving 1 or 2% of the response.

Jon Crosby said about 15 hours later

Update on the above: On the same machine, I see no issues under Leopard using the default version of Ruby on OS X 10.5. With a fresh install of Ubuntu 7.10 on that same hardware, curl, wget, gem update, etc. all fail with a timeout. This behavior is consistent even after multiple reboots on each OS and happens under both 1.1.0 and 1.1.1.

Jon Crosby said about 17 hours later

Just for some closure on the Ubuntu 7.10 issues: The root of the problem was IPv6 in Ubuntu conflicting with a router that didn’t support it. Upgrading the router this afternoon fixed the issue.

Jon Crosby said about 20 hours later

Add your comment

   Comment Markup Help | Preview comment