Theo Van Dinter replies in part:
> > 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 ?
I fixed the spec. so that the version number would read 3.0.2. I didn't show
the original run/failure when the version number was encoded as 3.000002.
Note: the rpm built from the tarball provided at spamassassin.org
(for spamassassin-3.0.2-1, and spamassassin-tools-3.0.2-1)
produced dependencies looking for version numbers of the form
3.0.2-1, _not_ 3.000002.
There appear to be only a few CPAN modules using this numbering convention:
# zgrep -P '^\S+\s+[0-9]+\.[0-9]{6}' 02packages.details.txt.gz
C::Sharp::Tokener 0.08062001 S/SI/SIMON/C-Sharp-0.01.tar.gz
Class::MakeMethods::Emulator::TakeName 1.000001
E/EV/EVO/Class-MakeMethods-1.0.14.tar.gz
File::Flock 104.111901
M/MU/MUIR/modules/File-Flock-104.111901.tar.gz
HTML::TableLayout 1.001008
S/SF/SFARRELL/HTML-TableLayout-1.001008.tar.gz
Mail::SpamAssassin 3.000002
F/FE/FELICITY/Mail-SpamAssassin-3.0.2.tar.gz
Math::Pari 2.010601
I/IL/ILYAZ/modules/Math-Pari-2.010601.tar.gz
POE::Component::Connection::Keepalive 1.000100010001
R/RC/RCAPUTO/POE-Component-Client-Keepalive-0.01.tar.gz
Proc::Forkfunc 96.041701
M/MU/MUIR/modules/Proc-Forkfunc-96.042201.tar.gz
Text::Tabs 98.112801
M/MU/MUIR/modules/Text-Tabs+Wrap-2001.0929.tar.gz
Tie::Array::Pointer 0.000059
B/BE/BEPPU/Tie-Array-Pointer-0.000059.tar.gz
Time::CTime 99.062201
M/MU/MUIR/modules/Time-modules-2003.1126.tar.gz
and those that do, seem to use the long number strings to encode the data of
release,
often as not.
>
> > (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.
>
Ovid (and I assume cpanflute) uses the CPAN registry info. to determine the
modules provided by a distribution. It also uses CPAN_VERSION if it exists
to construct the rpm name, if that field is present, otherwise it constructs
the name from the version info. in the distribution archive file name.
Therefore, it is helpful to others, if the CPAN information is correct,
consistent,
and up-to-date.
> > 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.
Don't the authors/contributors have some say over the info. recorded in
the CPAN database?
