Posted By: Eric Hodel
Date: 2008-11-03 19:29
Summary: RubyGems 1.3.1
Project: RubyGems

= Announce: RubyGems Release 1.3.1

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.1 fixes some bugs.

Bugs fixed:

* Disregard ownership of ~ under Windows while creating ~/.gem. Fixes
issues related to no uid support under Windows.
* Fix requires for Gem::inflate, Gem::deflate, etc.
* Make Gem.dir respect :gemhome value from config. (Note: this feature may be
removed since it is hard to implement on 1.9.)
* Kernel methods are now private. Patch #20801 by James M. Lawrence.
* Gem::location_of_caller now behaves on Windows. Patch by Daniel Berger.
* Silence PATH warning.

Deprecation Notices:

* Gem::manage_gems will be removed on or after March 2009.

For a full list of changes to RubyGems and the contributor for each change, see
the ChangeLog file.

Special thanks to Chad Wooley for backwards compatibility testing and Luis
Lavena for continuing windows support.

== 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
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

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)

Latest News
TZInfo::Data v1.2014.2 Released
    Philip Ross - 2014-03-25 22:32
TZInfo v0.3.39 Released
    Philip Ross - 2014-03-09 20:23
TZInfo::Data v1.2014.1 Released
    Philip Ross - 2014-03-09 20:00
Automatic Ruby 14.2.0 has been released!
    id 774 - 2014-02-26 06:23
kramdown 1.3.2 released
    Thomas Leitner - 2014-02-16 08:35

 

Forums | Admin

Discussion Forums: rubygems-1.3.1

Start New Thread Start New Thread

 

By: Peter Nash
RE: Problems on Windows environment [ reply ]  
2008-11-20 08:49
I had the same problem on just one out of 5 Windows machines (the other 4 upgraded OK). The difference was that the Ruby installation directory on that machine was "c:\Program Files\Ruby" whereas the others had Ruby in "C:\Ruby". This seemed to result in the file "c:\Program Files\Ruby\bin\gem.bat" containing an extra double-quote on lines 3 and 6. i.e. line 3 contained:

@"ruby.exe"" C:/Program Files/Ruby/bin/gem" %1 %2 %3 %4 %5 %6 %7 %8 %9

Removing the extra quote after ruby.exe on both lines fixed the problem for me.

By: Simone Roche
Problems on Windows environment [ reply ]  
2008-11-04 22:10
I've tried upgrading to this version and 1.3.0 from 1.2.0 without success. I get an error of "The filename, directory name, or volume label syntax is incorrect." after upgrading using the "ruby setup.rb install" command. I had a problem running the setup command with 1.3.0. but read the fix for line 713 and the install went fine. But after either "upgrade" I get that error. Is there an issue with the 1.3.* version for Windows???