RubyGems 1.3.0

drbrain@segment7.net (Eric Hodel) — Fri, 26 Sep 2008 14:19:00 -0700

Release 1.3.0 adds new features and fixes some bugs.

Note! Some versions of RubyGems have a bug that will prevent automatic updates. If RubyGems says it has nothing to update, run:

gem install rubygems-update
update_rubygems

New features:

RubyGems doesn't print LOCAL/REMOTE titles for `gem query` and friends if stdout is not a TTY, except with --both.
Added Gem.find_files, allows a gem to discover features provided by other gems.
Added pre/post (un)install hooks for packagers of RubyGems. (Not for gem themselves).
RubyGems now installs gems into ~/.gem if GEM_HOME is not writable. Use --no-user-install command-line switch to disable this behavior.
Fetching specs for update now uses If-Modified-Since requests.
RubyGems now updates the ri cache when the rdoc gem is installed and documentation is generated.

Deprecation Notices:

Gem::manage_gems now warns when called. It will be removed on or after March 2009.

Bugs Fixed:

RubyGems 1.3.0+ now updates when no previous rubygems-update is installed. Bug #20775 by Hemant Kumar.
RubyGems now uses the regexp we already have for `gem list --installed`. Bug #20876 by Nick Hoffman.
Platform is now forced to Gem::Platform::RUBY when nil or blank in the indexer. Fixes various uninstallable gems.
Handle EINVAL on seek. Based on patch in bug #20791 by Neil Wilson.
Fix HTTPS support. Patch #21072 by Alex Arnell.
RubyGems now loads all cache files even if latest has been loaded. Bug #20776 by Uwe Kubosch.
RubyGems checks for support of development dependencies for #to_ruby. Bug #20778 by Evan Weaver.
Now specifications from the future can be loaded.
Binary script uninstallation fixed. Bug #21234 by Neil Wilson.
Uninstallation with -i fixed. Bug #20812 by John Clayton.
Gem::Uninstaller#remove_all now calls Gem::Uninstaller#uninstall_gem so hooks get called. Bug #21242 by Neil Wilson.
Gem.ruby now properly escaped on windows. Fixes problem with extension compilation.
`gem lock --strict` works again. Patch #21814 by Sven Engelhardt.
Platform detection for Solaris was improved. Patch #21911 by Bob Remeika.

Other Changes Include:

`gem help install` now describes _version_ argument to executable stubs
`gem help environment` describes environment variables and ~/.gemrc and /etc/gemrc
On-disk gemspecs are now read in UTF-8 and written with a UTF-8 magic comment
Rakefile

If the SETUP_OPTIONS environment variable is set, pass its contents as arguments to setup.rb

lib/rubygems/platform.rb

Remove deprecated constant warnings and really deprecate them. (WIN32, etc).

lib/rubygems/remote_fetcher.rb
- Now uses ~/.gem/cache if the cache dir in GEM_HOME is not writable.
lib/rubygems/source_index.rb

Deprecate options to 'search' other than Gem::Dependency instances and issue warning until November 2008.

setup.rb

--destdir folder structure now built using Pathname, so it works for Windows platforms.

test/*

Fixes to run tests when under test/rubygems/. Patch by Yusuke ENDOH [ruby-core:17353].

test/test_ext_configure_builder.rb

Locale-free patch by Yusuke Endoh [ruby-core:17444].

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:

DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126
UNPACK INTO A DIRECTORY AND CD THERE
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)

"RubyGems 1.3.0" by Sebas

Thu, 09 Oct 2008 02:04:18 -0700

On ubuntu 8.04 I was getting /usr/bin/gem:10:Warning: Gem::manage_gems is deprecated and will be removed on or after March 2009.

to solve this problem I did:

selected pre-release and unsupported packages in Software Sources. apt-get remove ruby* apt-get clean apt-get install ruby rubygems

It helped me, you could try without selecting pre-release and unsupported packages, just some apt-get magic.

"RubyGems 1.3.0" by Doug Miller

Mon, 06 Oct 2008 15:57:10 -0700

c:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:713:in `set_paths’: undefined method `uid’ for nil:NilClass (NoMethodError)

I saw that this error was reported on 3/10/2008. I there a fix for this yet?

"RubyGems 1.3.0" by Eric Hodel

Wed, 01 Oct 2008 16:20:14 -0700

You should stop using Gem.manage_gems and require the files you want directly. Gem.manage_gems hasn’t done anything for several releases anyhow. It can probably just be deleted.

"RubyGems 1.3.0" by andy

Wed, 01 Oct 2008 11:33:29 -0700

Re: the deprecation message: - Gem::manage_gems now warns when called. - It will be removed on or after March 2009.

Is this a result of calling GemPackageTask.new ?? What should I use instead??

"RubyGems 1.3.0" by Dr Nic

Wed, 01 Oct 2008 05:55:38 -0700

Excellent, thx guys.

"RubyGems 1.3.0" by Eric Hodel

Tue, 30 Sep 2008 11:10:13 -0700

gem install rubygems-update; update_rubygems is the way to fix the “nothing to update” problem. Both 1.1 and 1.2 had this bug.

Unfortunately, fixing gem update—system takes at least two releases to be fixed.

"RubyGems 1.3.0" by MilesZS

Tue, 30 Sep 2008 07:14:02 -0700

Dr. Nic, I recommend “sudo gem install rubygems-update” and “sudo update_rubygems”. Be warned: I had to do this a while back, and now, apparently, must do this for every update. So, maybe it’s not at all the solution for which you were looking. It works, though.

"RubyGems 1.3.0" by Dr Nic

Tue, 30 Sep 2008 03:28:10 -0700

I managed to screw up my update process and now when I sudo gem update --system it says there is nothing to install, but gem env says I’m on 1.2.0 not 1.3.0. Is there a way to force a reupdate?

Segment7: RubyGems 1.3.0

RubyGems 1.3.0

How can I get RubyGems?

To File Bugs

Thanks

"RubyGems 1.3.0" by Sebas

"RubyGems 1.3.0" by Doug Miller

"RubyGems 1.3.0" by Eric Hodel

"RubyGems 1.3.0" by andy

"RubyGems 1.3.0" by Dr Nic

"RubyGems 1.3.0" by Eric Hodel

"RubyGems 1.3.0" by MilesZS

"RubyGems 1.3.0" by Dr Nic