Yes, I noticed that too.. Which is why I think something got messed up during an update. But then I went back to look at the "Last Modified" time for the files, and since that was some time ago (many days or more), so that didn't make sense, either.

But then I saw why.. The summary.ppm and searchsummary.ppm both list 1.24 as the current version. Things are starting to make sense.. But I still don't know if this is a problem with this particular repository or with the PPM system of tools--Or what can be done to handle it more gracefully. Nor does it explain why I get some of the same odd errors with other repositories and packages (which I have not yet been able to consistently reproduce, so might just be a httpd server issue--At this point, I'm even willing to believe it's got something to do with the alignment of the planets and phases of the moon, as long as it has a solution :-P)

Maybe some perlmonk will wake up and explain it all.. Until then, I will continue my own expedition into it.. ;-)

C. M.

Maybe some perlmonk will wake up and explain it all

Yes, sooner or later randyk will come along. He has a pretty good understanding of ppm. I find (the recent versions of) PPM annoyingly opaque, and I consequently try to stand well clear. There's a somewhat more transparent version of PPM on CPAN but, of course, it doesn't provide the features that are available with PPM3 and PPM4. It won't work with zip files (and therefore the trouchelle rep) either, though I've submitted a patch to rt.cpan that I think addresses that issue.

I notice that my ppm search ConfigReader-Simple produced  Downloading ActiveState Package Repository packlist but there was no corresponding action for the trouchelle rep. Therein, perhaps, lies the reason that you're still getting reports of 1.24 (instead of 1.25).

Cheers,
Rob