On Oct 11, 2007, at 16:30 , Luis Lavena wrote: > On 10/11/07, Eric Hodel <[EMAIL PROTECTED]> wrote: >> I fear it is an existing bug that hasn't yet been discovered. People >> are reporting "missing" gems with 0.9.4 with bulk updates of the YAML >> index with the same symptoms you are showing. > > I've experienced that with 0.9.4 too. Not with the beta... seems odd. > > Sometimes requesting the install again works ok, sometimes I need to > clear the cache...
I think the new Marshal index hides it better. >> I think it is ok to push a beta tonight, then. > > Yeah, I broad audience could be more helpful. > > I found also that unpacking certain kind of gems brake the Zlib > package... which is now fixed in the trunk. > > Could be possible add a "--debug" option to get the backtrace when "no > gem NAME found" is shown? maybe that could provide us more information > to pin-point the problem. $ gem install --debug no_such_gem Exception `NameError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ command_manager.rb:132 - uninitialized constant Gem::Commands::InstallCommand Exception `Gem::GemNotFoundException' at /usr/local/lib/ruby/ site_ruby/1.8/rubygems/dependency_installer.rb:75 - could not find no_such_gem locally or in a repository ERROR: could not find no_such_gem locally or in a repository Since the exception gets rescued, you don't get a backtrace, but this is good enough. I think I can find the error, but I don't think its worth delaying the beta for it. -- Poor workers blame their tools. Good workers build better tools. The best workers get their tools to do the work for them. -- Syndicate Wars _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
