>>>>> On 15 Dec 2004 17:00:19 -0800, [EMAIL PROTECTED] (Randal L. Schwartz) >>>>> said:
Andreas> As a stop-gap solution I manually issued a mysql> delete from packages where package like 'Apache::Test%' and dist like '%mod_perl-2%'; > Please also do this for Apache::Resource. Right now, CPAN.pm is telling > me that mod_perl has a newer Apache::Resource than I can find in the CPAN, > wanting me to install mod_perl2. > This is a problem that arose now only because you are now indexing > mod_perl2 as mainstream. > Stas says it's a problem with the indexing stuff. I'm not entirely > sure of that, but I'm not entirely sure it's not a misunderstanding > by Stas of how real world people have only one @INC for their box. >> From what I gather, the Apache::Resource in mod_perl2 is *not* upward > compatible with the one in the CPAN (for mod_perl1), and yet they're > reusing the same name. Yuck. If that's the case, the whole release > is tainted. I did the same for Apache::Resource but did not schedule a re-indexing run for whatever distribution should be associated with it. So after the next run of the indexer, CPAN.pm will simply NOT KNOW what Apache::Resource is. This seems preferable to me to pointing to the wrong distribution. Stas, can you please make sure that the right distribution gets reindexed? If you cannot, please tell me which should, then I can care for the right scheduling. -- andreas
