On Mar 28, 2008, at 22:10 PM, Chad Woolley wrote: > On Fri, Mar 28, 2008 at 9:55 PM, Chad Woolley > <[EMAIL PROTECTED]> wrote: >> I'm still seeing wierdness here. First of all, when I do a remote >> list for capistrano on rubyforge, I only find cap 2.2.0. I know >> there >> was a 2.0.0 and 2.1.0, but it is not shown.
Nope. `gem list -r --all cap` to force a bulk update. 99% of the time you don't care about anything other than the latest, so RubyGems will no longer keep up to date for past revisions. If you want to install a particular version, RubyGems will go looking for it. (This could now be made even smarter, but I currently lack the energy.) >> Also, it keeps updating the cache over and over when there is a >> failure to find a gem, even with the same user. >> >> This is on default Leopard ruby install, I'm pretty sure with a gem >> update --system to 1.0.1, but I might have installed a recent trunk >> with setup and forgot about it. > > Update - this was definitely with trunk installed (after recent > caching changes), and definitely was fixed by reinstalling 1.0.1 from > setup.rb. I didn't have to manually blow away ~/.gem, just > reinstalling 1.0.1 fixed it. I just fixed the last bug with the quick/latest index code. It seems to be ok now. _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
