Bug 3736 - require_version and floating point precision? (3.00 RC2)
Summary: require_version and floating point precision? (3.00 RC2)
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: PC Linux
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-29 17:37 UTC by Bart Schaefer
Modified: 2004-08-30 07:16 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bart Schaefer 2004-08-29 17:37:55 UTC 
This output from "spamassassin --lint" seems a bit off-kilter:

configuration file "/etc/mail/spamassassin/local.cf" requires version 3.00 of
SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C
switch, or remove the old config files? Skipping this file at
/home/sites/site35/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/Conf/Parser.pm
line 329.
Comment 1 Theo Van Dinter 2004-08-29 18:37:46 UTC 
Subject: Re:  New: require_version and floating point precision?  (3.00 RC2)

On Sun, Aug 29, 2004 at 05:37:56PM -0700, bugzilla-daemon@bugzilla.spamassassin.org wrote:
> configuration file "/etc/mail/spamassassin/local.cf" requires version 3.00 of
> SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C
> switch, or remove the old config files? Skipping this file at
> /home/sites/site35/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/Conf/Parser.pm
> line 329.

It looks like your local.cf has "require_version 3.00", which isn't valid.
Per the docs, the version needs to be in the same format as the internal
version number: x.yyyzzz.
Comment 2 Bart Schaefer 2004-08-30 11:49:56 UTC 
Aha.  I suggest a note about this be added to the UPGRADE file.
Comment 3 Theo Van Dinter 2004-08-30 15:16:35 UTC 
well, "require_version" hasn't changed wrt wanting a parameter of the version in internal representation 
format.  I'll add in a paragraph that the UPGRADE doc is probably not complete and you'll want to check 
any custom configuration to make sure it's valid in the new version.