RubyGems 1.0.1

Eric Hodel | Fri, 21 Dec 2007 03:25:37 GMT

Posted in ,

Release 1.0.1 fixes a few bugs.

Bugs Fixed:

  • Installation on Ruby 1.8.3 through 1.8.5 fixed
  • gem build on 1.8.3 fixed

Other Changes Include:

  • Since RubyGems 0.9.5, RubyGems is no longer supported on Ruby 1.8.2 or older, this is official in RubyGems 1.0.1.

How can I get RubyGems?

NOTE: If you have installed RubyGems using a package 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:

To File Bugs

The RubyGems bug tracker can be found on RubyForge at: http://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)

3 comments

Comments RSS FEED

Great, I just installed at my Macbook and I can report that everything went fine. Kudos for the 1.0 release!

AkitaOnRails said about 15 hours later

Windows platform is still broken. Steps to reproduce:

  1. Install the latest One-Click Ruby Installer for Windows (1.8.6-26)
  2. Upgrade RubyGems to 1.0.1 using gem update --system
  3. Upgrade win32-api gem via gem update win32-api from 1.0.4 (default) to 1.0.5
  4. RubyGems fails trying the “ruby” platform, not the mswin32
  5. gem env shows “ruby” platform first followed by “x86-mswin32-60” as second

I had the same problem with RubyGems 0.9.5 and json gem, but I haven’t tried it with RubyGems 1.0.1 yet.

Nikolay Kolev said about 24 hours later

Nikolay, can you file a bug for me in the tracker? Thanks.

Eric Hodel said 2 days later

Comments are disabled