[Rubygems-developers] [ rubygems-Bugs-27048 ] Cannot use rubygems-update 1.3.5 to update from rubygems 1.2.x installation

noreply at rubyforge.org noreply at rubyforge.org
Wed Apr 21 23:15:50 EDT 2010


Bugs item #27048, was opened at 2009-09-04 00:10
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=27048&group_id=126

Category: `gem` commands (other)
>Group: v1.3.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Alain Hoang (hoanga)
>Assigned to: Eric Hodel (drbrain)
Summary: Cannot use rubygems-update 1.3.5 to update from rubygems 1.2.x installation

Initial Comment:
Hi,

I ran into a case where if had an older installation of Rubygems 1.2.0 then tried to install rubygems-update 1.3.5 and tried to use the update_rubygems command you would get an error like the following:

`report-activate-error': Could not find RubyGem session (>= 0) 
(Gem::LoadError)


This makes it impossible to update rubygems from version 1.3.5 of rubygems-update.  But it IS possible with version 1.3.4 of rubygems-update.

I consider this behavior extremely unfriendly for people who are on rubygems 1.2.x and want to use a provided mechanism for upgrading

I believe in the email thread below.  Someone else also gets a similar stack trace and their solution was to upgrade from source:

http://www.pubbs.net/ruby/200907/68654/


It would be much more preferred to be able to update rubygems via version 1.3.5 (and beyond) of rubygems-update.  But what is considered the canonical way to upgrade?


----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2010-04-21 20:15

Message:
Fixed in 1.3.6

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=27048&group_id=126


More information about the Rubygems-developers mailing list