On 5/7/07, Jim Weirich <[EMAIL PROTECTED]> wrote: > On 5/7/07, Chad Woolley <[EMAIL PROTECTED]> wrote: > > Just providing closure on this. I got no response, here or on the > > jruby list, so I monkey-patched rubygems to do an exact name match for > > 'gem list'. That fixed my problem, since all I care about is making > > it work when called programmatically from my app. > > > > I still think it's kind of an issue if "gem list activerecord > > --remote" throws an exception, but oh well :) > > Chad, > > Sorry for the late response ... things have finally slowed down a bit here. > > I've tried this on the platforms I have available (MacOS, Ubuntu) and > don't see the same problem. > > By the error trace it seems that the program is aborting in the middle > of the version comparison software (to_ints converts "1.2.3" to [1, 2, > 3]). Since the trace complains about a YAML object, I'm suspecting > that the version data is somehow bogus. The YAML data comes from the > local source index cache, so maybe your source index cache is > corrupted. Try this: > > (1) Save your current source index cache somewhere. > (2) Delete current source index cache. > (3) Rerun gem list --remote (it will automatically regenerate the cache). > > If the problem goes away, then we can blame the cache. At that point, > I would like to see the file, so send me the file you saved in step 1 > above). > > If the problem persists, then it is something else ... and i'll have > to think harder. > > -- Jim Weirich
Hi Jim, I know I did those steps on at least one of the machines (blow away source index), and the problem persisted. I'll try again though, and send you the failing file. Thanks, Chad _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
