On Feb 22, 2011, at 12:33 , James Tucker wrote:
> Hey all, Ryan in particular,
>
> I think this is endemic to some other issue, but I have limited time right
> now to debug.
>
> The following works fine:
>
> raggi@mbk: ~ * irb
>>> require 'rubygems'
> => true
>>> Gem.activate('rails', '< 3.0.0.beta')
> => true
>
> The following goes into an infinite loop:
>
> raggi@mbk: ~ * irb
>>> require 'rubygems'
> => true
>>> Gem.activate('rails', '< 3.0.0.b')
>
>
> Replication environment:
>
> % g log -n 1 --oneline
> 9144463 Add missing require of RemoteFetcher to the unpack command
> % ruby -v
> ruby 1.8.7 (2010-12-23 patchlevel 330) [i686-darwin10]
> % gem list rails
>
> *** LOCAL GEMS ***
>
> rails (3.0.4, 3.0.3, 3.0.1, 3.0.0.rc, 3.0.0.beta4, 2.3.9.pre)
>
>
> It's probably related to prerelease version but I'm not certain. I'll dump
> out all the active* and action* if necessary too, just let me know.
I can't repro. I installed all the above versions and get:
10016 % git log -n 1 --oneline
615a5cf Add failing test for the try_activate failure case of lazy activation.
Test is currently non-working I think due to util methodology
10017 % gitx
10018 % git log C-c C-c
10018 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.b"); p
Gem.loaded_specs.keys.sort'
["rails"]
10019 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.beta"); p
Gem.loaded_specs.keys.sort'
["rails"]
I don't even see how an infinite loop is possible given that the real change I
made to Gem.activate was to remove the recursion.
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
