On Wed, Mar 26, 2008 at 8:13 AM, Chad Woolley <[EMAIL PROTECTED]> wrote: > On Tue, Mar 25, 2008 at 10:13 PM, Assaph Mehr <[EMAIL PROTECTED]> wrote: > > Silly question: did you do a gem list/search as a regular user > > followed by a gem install as sudo? There would be 2 different caches > > in this case that will be updated... > > Yeah, that's what must have happened. Thanks. >
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. 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. Probably just something with my system, but thought I'd report it anyway. _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
