# RubyGems 1.3.7

**URL:** <https://www.ruby-forum.com/t/rubygems-1-3-7/188577>\
**Category:** Ruby\
**Created:** [May 14, 2010, 6:54am UTC](https://www.ruby-forum.com/t/rubygems-1-3-7/188577 "2010-05-14T06:54:03Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![miracleofmagick](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/71c47a/32.png) [@miracleofmagick](https://www.ruby-forum.com/u/miracleofmagick)\
**Post date:** [May 14, 2010, 6:54am UTC](https://www.ruby-forum.com/t/rubygems-1-3-7/188577/1 "2010-05-14T06:54:03Z")

</div>

rubygems version 1.3.7 has been released!

- [http://rubygems.org/](http://rubygems.org/)
- [http://docs.rubygems.org/](http://docs.rubygems.org/)
- [http://rubygems.rubyforge.org/](http://rubygems.rubyforge.org/)
- [http://rubyforge.org/projects/rubygems](http://rubyforge.org/projects/rubygems)

RubyGems is a package management framework for Ruby.

This gem is an update for the RubyGems software. You must have an  
installation of RubyGems before this update can be applied.

See Gem for information on RubyGems (or `ri Gem`)

To upgrade to the latest RubyGems, run:

$ gem update --system # you might need to be an administrator or root

NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no  
rubygems-update installed. You will need to use the following  
instructions  
if you see “Nothing to update”.

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 RubyGems install, there is still the pre-gem  
approach to  
getting software, doing it manually:

1. Download from: [http://rubyforge.org/frs/?group\_id=126](http://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

For more details and other options, see:

ruby setup.rb --help

Changes:

### 1.3.7 / 2010-05-13

NOTE:

[http://rubygems.org](http://rubygems.org) is now the default source for downloading gems.

You may have sources set via ~/.gemrc, so you should replace  
[http://gems.rubyforge.org](http://gems.rubyforge.org) with [http://rubygems.org](http://rubygems.org)

[http://gems.rubyforge.org](http://gems.rubyforge.org) will continue to work for the forseeable  
future.

New features:

- `gem` commands
  - `gem install` and `gem fetch` now report alternate platforms when a  
matching one couldn’t be found.
  - `gem contents` --prefix is now the default as specified in --help.  
Bug  
#27211 by Mamoru T…
  - `gem fetch` can fetch of old versions again. Bug #27960 by Eric  
Hankins.
  - `gem query` and friends output now lists platforms. Bug #27856 by  
Greg  
Hazel.
  - `gem server` now allows specification of multiple gem dirs for  
documentation. Bug #27573 by Yuki S…
  - `gem unpack` can unpack gems again. Bug #27872 by Timothy Jones.
  - `gem unpack` now unpacks remote gems.
  - –user-install is no longer the default. If you really liked it,  
see  
Gem::ConfigFile to learn how to set it by default. (This change was  
made  
in 1.3.6)

- RubyGems now has platform support for IronRuby. Patch #27951 by Will  
Green.

Bug fixes:

- Require rubygems/custom\_require if --disable-gem was set. Bug #27700  
by  
Roger P…
- RubyGems now protects against exceptions being raised by plugins.
- rubygems/builder now requires user\_interaction. Ruby Bug #1040 by  
Phillip  
Toland.
- Gem::Dependency support #version\_requirements= with a warning. Fix  
for old  
Rails versions. Bug #27868 by Wei Jen Lu.
- Gem::PackageTask depends on the package dir like the other rake  
package  
tasks so dependencies can be hooked up correctly.

---

<div class="post-metadata">

**Author:** ![miracleofmagick](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/71c47a/32.png) [@miracleofmagick](https://www.ruby-forum.com/u/miracleofmagick)\
**Post date:** [May 14, 2010, 4:30pm UTC](https://www.ruby-forum.com/t/rubygems-1-3-7/188577/2 "2010-05-14T16:30:40Z")

</div>

Eric H. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> - RubyGems now protects against exceptions being raised by plugins.

This sounds great. It turned out that rdoc\_osx\_dictionary, with its  
rubygems plugin, was what was killing my gems, rdoc, and the whole bit.  
The situation was so bad that I couldn’t even get gem to uninstall  
rdoc\_osx\_dictionary - I had to rip it physically out of the computer in  
order for gem to work at all. It sounds like this feature will protect  
against this kind of vicious circle. m.

---

<div class="post-metadata">

**Author:** ![miracleofmagick](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/71c47a/32.png) [@miracleofmagick](https://www.ruby-forum.com/u/miracleofmagick)\
**Post date:** [May 14, 2010, 4:36pm UTC](https://www.ruby-forum.com/t/rubygems-1-3-7/188577/3 "2010-05-14T16:36:32Z")

</div>

On May 13, 2010, at 11:53 PM, Eric H. wrote:

> rubygems version 1.3.7 has been released!

Thanks for your continued work on this! What a great contribution to the  
community…

cr

---

<div class="post-metadata">

**Author:** ![miracleofmagick](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/71c47a/32.png) [@miracleofmagick](https://www.ruby-forum.com/u/miracleofmagick)\
**Post date:** [May 14, 2010, 7:39pm UTC](https://www.ruby-forum.com/t/rubygems-1-3-7/188577/4 "2010-05-14T19:39:52Z")

</div>

On May 14, 2010, at 09:21, Wayne E. Seguin wrote:

> One question, when I go to [http://rubyforge.org/frs/?group\_id=126](http://rubyforge.org/frs/?group_id=126) I do  
> not see a 1.3.7 release, has it not updated yet?

Looks like I still need to do some work on the release portion of the  
Rakefile, maybe next release will do this automatically again. I’ve put  
them up by hand.

---

<div class="post-metadata">

**Author:** ![miracleofmagick](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/71c47a/32.png) [@miracleofmagick](https://www.ruby-forum.com/u/miracleofmagick)\
**Post date:** [May 14, 2010, 6:22pm UTC](https://www.ruby-forum.com/t/rubygems-1-3-7/188577/5 "2010-05-14T18:22:54Z")

</div>

Eric,

Nice job on the release.

One question, when I go to [http://rubyforge.org/frs/?group\_id=126](http://rubyforge.org/frs/?group_id=126) I do  
not see a 1.3.7 release, has it not updated yet?

Thanks!

~Wayne

---

<div class="post-metadata">

**Author:** ![miracleofmagick](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/71c47a/32.png) [@miracleofmagick](https://www.ruby-forum.com/u/miracleofmagick)\
**Post date:** [June 30, 2010, 5:05pm UTC](https://www.ruby-forum.com/t/rubygems-1-3-7/188577/6 "2010-06-30T17:05:37Z")

</div>

On Jun 30, 10:57 am, Roger P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Installing RubyGems 1.3.7  
> ERROR: While executing gem … (Gem::Exception)  
> [BUG] invalid exec\_format “ir”, no %s  
> RubyGems system software updated
> 
> C:\dev\ruby\downloads\rubygems-1.3.7\>ir setup.rb  
> ERROR: While executing gem … (Gem::Exception)  
> [BUG] invalid exec\_format “ir”, no %s

No, you can’t update IronRuby with gem update --system

Use a IronRuby R.Gems 1.3.7 powered version, which is latest one.

---

<div class="post-metadata">

**Author:** ![miracleofmagick](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/71c47a/32.png) [@miracleofmagick](https://www.ruby-forum.com/u/miracleofmagick)\
**Post date:** [June 30, 2010, 5:33pm UTC](https://www.ruby-forum.com/t/rubygems-1-3-7/188577/7 "2010-06-30T17:33:38Z")

</div>

> No, you can’t update IronRuby with gem update --system

Appears that currently you can’t update it by running setup.rb,  
either…

> Use a IronRuby R.Gems 1.3.7 powered version, which is latest one.

for me 1.0.0v4 came with 1.3.5

Perhaps there is some newer version available that I’m unaware of?  
-r

---

<div class="post-metadata">

**Author:** ![miracleofmagick](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/71c47a/32.png) [@miracleofmagick](https://www.ruby-forum.com/u/miracleofmagick)\
**Post date:** [June 30, 2010, 3:57pm UTC](https://www.ruby-forum.com/t/rubygems-1-3-7/188577/8 "2010-06-30T15:57:25Z")

</div>

> - RubyGems now has platform support for IronRuby. Patch #27951 by Will  
> Green.

Hmm. Perhaps it could use a bit more IR love?

C:\dev\digitalarchive\_trunk\>igem update --system  
Updating RubyGems  
Updating rubygems-update  
Successfully installed rubygems-update-1.3.7  
Updating RubyGems to 1.3.7  
Installing RubyGems 1.3.7  
ERROR: While executing gem … (Gem::Exception)  
[BUG] invalid exec\_format “ir”, no %s  
RubyGems system software updated

C:\dev\ruby\downloads\rubygems-1.3.7\>ir setup.rb  
ERROR: While executing gem … (Gem::Exception)  
[BUG] invalid exec\_format “ir”, no %s

---

<div class="post-metadata">

**Author:** ![miracleofmagick](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/71c47a/32.png) [@miracleofmagick](https://www.ruby-forum.com/u/miracleofmagick)\
**Post date:** [June 30, 2010, 7:34pm UTC](https://www.ruby-forum.com/t/rubygems-1-3-7/188577/9 "2010-06-30T19:34:21Z")

</div>

On Wed, Jun 30, 2010 at 10:33 AM, Roger P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> > No, you can’t update IronRuby with gem update --system
> 
> Appears that currently you can’t update it by running setup.rb,  
> either…
> 
> > Use a IronRuby R.Gems 1.3.7 powered version, which is latest one.
> 
> for me 1.0.0v4 came with 1.3.5

I was getting the same error. Will G. posted a fix on his blog  
[http://hotgazpacho.org/2010/05/ironruby-gem-update-system/](http://hotgazpacho.org/2010/05/ironruby-gem-update-system/) . I was  
able to upgrade to 1.3.7 after adding that file.

C:\>ir -S gem update --system

> Perhaps there is some newer version available that I’m unaware of?

I don’t see anything newer on codeplex or rubyforge.
