On Jun 5, 2008, at 21:40 PM, Chad Woolley wrote:
On Tue, Jun 3, 2008 at 11:30 PM, Chad Woolley
<[EMAIL PROTECTED]> wrote:
opened a bug here:
http://rubyforge.org/tracker/index.php?func=detail&aid=20509&group_id=126&atid=575
Update on this. config-file seems to be a red herring. Real problem
is that the trunk "gem list --remote" is reporting local system gems
that are not in the servers dir, when the list command is run the
*second* time. See details with commands to reproduce on the ticket.
Anyone else seeing this?
Fixed in 1756.
I made Gem::SourceIndex track where it got loaded from, so #refresh!
will always refresh from the same paths. (It also now raises if the
SourceIndex wasn't created from a directory.)
_______________________________________________
Rubygems-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rubygems-developers
