On 5/7/07, Jim Weirich <[EMAIL PROTECTED]> wrote: > > Try again and blow both caches away.
Jim, Thanks for looking at this. Deleting ~/.gem/source_cache did make the problem go away. It comes back when I do a remote list against a non-mirror gem server I set up for my company. Indeed, even a list of all gems on this server causes the same error, so I think the ActiveRecord-JDBC thing is a red herring - it just happens to be the first one in alphabetical order. The problem is probably with the yaml index on our server, which doesn't surprise me, because I am generating it with a hacked index_gem_repository command. Another co-worker reported this same problem with his personal machine, in a thread on April 11th, titled "index_gem_repository problem". Basically, the command fails on some gems: http://rubyforge.org/pipermail/rubygems-developers/2007-March/002632.html I get the same errors Steve described in that thread, and I'm even running against a different server. I'm hitting rsync://rubyforge.rubyuser.de/gems (which I was told about in a private email before that webpage went up), and Steve is hitting the one on the webpage (rubyforge.lauschmusik.de/gems/). The instructions for this are from here: http://rubyforge.org/docman/view.php/5/231/mirror_setup.html So, I think the root cause is something with mirroring gems via rsync for a non-public server, which seems to cause problems with index_gem_repository, forcing us to hack it and result in a seemingly buggy yaml file. I will send you the address of our private server's yaml file via personal mail, so you can check it out. I'm still very willing to help debug this issue, because we want to have a working private gem mirror. Thanks, Chad _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
