On Mon, Dec 27, 2004 at 03:48:26PM -0800, Gary Funck wrote: > CPAN_VERSION 3.000002 > I believe that should read CPAN_VERSION 3.0.2 above.
To work around CPAN/other perl module issues (namely that 3.0.2 isn't easily considered a version by most things), internally SpamAssassin uses the perl versioning trick: x.yyyzzz. So 3.000002 internally is really 3.0.2, which we convert on display. > When I tried the install: > # !rpm > rpm -Uvh spamassassin-3.0.2-1.i386.rpm spamassassin-tools-3.0.2-1.i386.rpm > perl-Mail-SpamAssassin-3.0.2-1.i386.rpm perl-Parse-Syslog-1.03-1.i386.rpm Didn't you just say that the RPM came out 3.000002 ? > (clearly the suggested resolution is bogus). The difficulty, > it seems, is that when Ovid packaged the rpm > perl-Mail-SpamAssassin-3.0.2-1.i386.rpm, It didn't find info. > in the CPAN database leading it to believe that Mail::Spamassassin > in fact provides Mail::SpamAssassin::ArchiveIterator, > Mail::SpamAssassin::Message, and Mail::SpamAssassin::PerMsgLearner. That's not CPAN's job. The rpmbuild process will call the appropriate RPM scripts (/usr/lib/rpm/find-provides) to find what modules the RPM will provide and then sets that appropriately in the package. > In summary, > - The CPAN_VERSION for Mail::Spamassassin should be 3.0.2. Please see above. > - The current distribution for the various Mail:Spamassassin > modules should be bumped to the current 3.0.2 distribution. > - The modules Mail::SpamAssassin::ArchiveIterator, > Mail::SpamAssassin::Message, and Mail::SpamAssassin::PerMsgLearner > should be listed in the CONTAINSMODS entry. > - Are all the older pre- 3.x entries still needed? These are all up to CPAN, as far as I know, we have no control over them. -- Randomly Generated Tagline: "HR people are generally capable of producing swank holiday parties and finding a dentist in your HMO group, but don't count on them to help you find a job." - David Clark
pgpESN630kBU0.pgp
Description: PGP signature
