RubyGems 1.3.5

rubygems-update version 1.3.5 has been released!

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 install --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
  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.5 / 2009-07-21

Bug fixes:

  • Fix use of prerelease gems.
  • Gem.bin_path no longer escapes path with spaces. Bug #25935 and
    #26458.

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.

Didn’t you mean…

gem update --system

Using Windows Vista…

Updated to RubyGems 1.3.5…

gem -v shows 1.3.4
gem list shows rubygems-update(1.3.5) and nothing else.

I even tried the commands out while within C:\ruby\bin which is the only
path variable set in my environment.

Any idea what happened?

Hrm…

Well for some reason, all my gems still work and I still show the old
environment except for when I do a gem list now that I upgraded. I did
a gem env and see the following on windows:

RubyGems Environment:

My best guess here (and I’m no expert on rubygems) is that there are two
gem paths and the the latter one (c:/Users/Joel/.gem/ruby/1.8) is the
one that this latest update defaulted to for some reason.

How do I remove just that gem path from GEM PATHS so that
/lib/ruby/gems/1.8 remains?

/lib/ruby/gems/1.8 from C:\ruby contains all of my gems… I searched the
web and can’t find any instructions on removing a specific GEM PATH.

Eric H. wrote:

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

No luck on WinXP:

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

E:>gem -v
1.2.0

E:>gem install rubygems-update
Successfully installed rubygems-update-1.3.5
1 gem installed
Installing ri documentation for rubygems-update-1.3.5…
Installing RDoc documentation for rubygems-update-1.3.5…
Could not find main page README
Could not find main page README
Could not find main page README
Could not find main page README

E:>update_rubygems
e:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:578:in
report_activate_error': Could not find RubyGem session (>= 0) (Gem::LoadError) from e:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:134:inactivate’
from e:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:158:in
activate' from e:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:157:ineach’
from e:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:157:in
activate' from e:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:49:ingem’
from e:/ruby/bin/update_rubygems:18

E:\vjoel>gem -v
1.2.0

If you don’t have any RubyGems install, there is still the pre-gem
approach to
getting software, doing it manually:

Will try that.

On Jul 21, 2009, at 18:39, Joel VanderWerf wrote:

© Copyright 1985-2001 Microsoft Corp.
from e:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:134:in
1.2.0
Ah, you probably got bitten by the development dependencies :confused:

If you don’t have any RubyGems install, there is still the pre-gem
approach to
getting software, doing it manually:

Will try that.

It should work.

On Jul 21, 2009, at 17:23, Älphä Blüë wrote:

Didn’t you mean…

gem update --system

Yes, sorry. I’ve fixed it on my blog post and on rubyforge.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs