# RubyGems 1.3.4

**URL:** <https://www.ruby-forum.com/t/rubygems-1-3-4/169164>\
**Category:** Ruby\
**Created:** [May 30, 2009, 4:23pm UTC](https://www.ruby-forum.com/t/rubygems-1-3-4/169164 "2009-05-30T16:23:33Z")\
**Posts on this page:** 1\
**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 30, 2009, 4:23pm UTC](https://www.ruby-forum.com/t/rubygems-1-3-4/169164/1 "2009-05-30T16:23:33Z")

</div>

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

Release 1.3.4 fixes some bugs and adds some features.

Bug Fixes:

- Fixed various warnings
- Gem::ruby\_version works correctly for 1.8 branch and trunk
- Prerelease gems now show up in `gem list` and can be used
- Fixed option name for `gem setup --format-executable`
- RubyGems now matches Ruby \> 1.9.1 gem paths
- Gem::RemoteFetcher#download now works for explicit Windows paths  
across  
drives. Bug #25882 by Lars C.
- Fix typo in Gem::Requirement#parse. Bug #26000 by Mike G…

Deprecation Notices:

- Bulk index update is no longer supported (the code currently  
remains, but not  
the tests)
- Gem::manage\_gems was removed in 1.3.3.
- Time::today was removed in 1.3.3.

For a full list of changes to RubyGems and the contributor for each  
change, 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: RubyGems 1.1 and 1.2 have problems upgrading when there is no  
rubygems-update installed. You will need to follow the second set of  
update  
instructions if you see “Nothing to update”.

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: [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)

== To File Bugs

The RubyGems bug tracker can be found on RubyForge at:  
[http://rubyforge.org/tracker/?func=add&group\_id=126&atid=575](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!

– The RubyGems team