You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Robert Nicholson <ro...@gmail.com> on 2014/04/11 03:11:19 UTC
Differences b/w 3.3.0 and 3.4.0?
My first attempt an integrating 3.4.0 (hopefully to solve the DnsResolver.pm Invalid Argument issue) ends up with
Subroutine NetAddr::IP::STORABLE_freeze redefined at /usr/local/lib64/perl5/NetAddr/IP.pm line 362.
at /usr/local/lib64/perl5/NetAddr/IP.pm line 362.
NetAddr::IP::import("NetAddr::IP") called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
Mail::SpamAssassin::NetSet::BEGIN() called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
eval {...} called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
require Mail/SpamAssassin/NetSet.pm called at /usr/share/perl5/Mail/SpamAssassin/Conf.pm line 86
Mail::SpamAssassin::Conf::BEGIN() called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
eval {...} called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
my perlscript that invokes
use Mail::SpamAssassin;
use Mail::SpamAssassin::Message;
use Mail::SpamAssassin::PerMsgStatus;
use Mail::SpamAssassin::PluginHandler;
my $spamtest = new Mail::SpamAssassin({
PREFIX => $PREFIX,
DEF_RULES_DIR => $DEF_RULES_DIR,
LOCAL_RULES_DIR => $LOCAL_RULES_DIR,
LOCAL_STATE_DIR => $LOCAL_STATE_DIR,
userprefs_filename => "$PREFIX/.spamassassin/user_prefs",
userstate_dir => "$PREFIX/.spamassassin",
debug => $debugLevel,
local_tests_only => $local eq '1'
});
Is there anything obvious that causes this to fail?
Why does the UPGRADE file start with
Note for Users Upgrading to SpamAssassin 3.3.0
Re: Differences b/w 3.3.0 and 3.4.0?
Posted by Benny Pedersen <me...@junc.eu>.
Robert Nicholson skrev den 2014-04-11 04:45:
> Well I appear to have gotten it working..
all ?
> For now everything works if I simply comment out the NetAddr::IP in
> NetSet.pm
show "spamassassin 2>&1 -D --lint" here
i think you just need more updates
Re: Differences b/w 3.3.0 and 3.4.0?
Posted by Mark Martinec <Ma...@ijs.si>.
Robert Nicholson wrote:
>> My first attempt an integrating 3.4.0 (hopefully to solve the
>> DnsResolver.pm Invalid Argument issue) ends up with
>>
>> Subroutine NetAddr::IP::STORABLE_freeze redefined at
>> /usr/local/lib64/perl5/NetAddr/IP.pm line 362.
>> at /usr/local/lib64/perl5/NetAddr/IP.pm line 362.
>> NetAddr::IP::import("NetAddr::IP") called at
>> /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
>> Mail::SpamAssassin::NetSet::BEGIN() called at
>> /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
>> eval {...} called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm
>> line 26
>> require Mail/SpamAssassin/NetSet.pm called at
>> /usr/share/perl5/Mail/SpamAssassin/Conf.pm line 86
>> Mail::SpamAssassin::Conf::BEGIN() called at
>> /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
>> eval {...} called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm
>> line 26
>>
>> my perlscript that invokes
>>
>> use Mail::SpamAssassin;
>> use Mail::SpamAssassin::Message;
>> use Mail::SpamAssassin::PerMsgStatus;
>> use Mail::SpamAssassin::PluginHandler;
>>
>> my $spamtest = new Mail::SpamAssassin({
>> PREFIX => $PREFIX,
>> DEF_RULES_DIR => $DEF_RULES_DIR,
>> LOCAL_RULES_DIR => $LOCAL_RULES_DIR,
>> LOCAL_STATE_DIR => $LOCAL_STATE_DIR,
>> userprefs_filename => "$PREFIX/.spamassassin/user_prefs",
>> userstate_dir => "$PREFIX/.spamassassin",
>> debug => $debugLevel,
>> local_tests_only => $local eq '1'
>> });
>>
>> Is there anything obvious that causes this to fail?
Strange. I can't reproduce this. Was anything significant left out from
the
above test program? What version of perl and what version of NetAddr::IP
?
> Well I appear to have gotten it working..
> For now everything works if I simply comment out the NetAddr::IP in
> NetSet.pm
Good for you. It looks like a warning anyway...
Appears like NetAddr::IP is being forcibly 'required' twice
(perhaps even different versions), although even so I can't reproduce
it.
>> Why does the UPGRADE file start with
>> Note for Users Upgrading to SpamAssassin 3.3.0
A mistake. Fixed in trunk in February.
Mark
Re: Differences b/w 3.3.0 and 3.4.0?
Posted by Robert Nicholson <ro...@gmail.com>.
Well I appear to have gotten it working..
For now everything works if I simply comment out the NetAddr::IP in NetSet.pm
On Apr 10, 2014, at 8:11 PM, Robert Nicholson <ro...@gmail.com> wrote:
> My first attempt an integrating 3.4.0 (hopefully to solve the DnsResolver.pm Invalid Argument issue) ends up with
>
> Subroutine NetAddr::IP::STORABLE_freeze redefined at /usr/local/lib64/perl5/NetAddr/IP.pm line 362.
> at /usr/local/lib64/perl5/NetAddr/IP.pm line 362.
> NetAddr::IP::import("NetAddr::IP") called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
> Mail::SpamAssassin::NetSet::BEGIN() called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
> eval {...} called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
> require Mail/SpamAssassin/NetSet.pm called at /usr/share/perl5/Mail/SpamAssassin/Conf.pm line 86
> Mail::SpamAssassin::Conf::BEGIN() called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
> eval {...} called at /usr/share/perl5/Mail/SpamAssassin/NetSet.pm line 26
>
> my perlscript that invokes
>
> use Mail::SpamAssassin;
> use Mail::SpamAssassin::Message;
> use Mail::SpamAssassin::PerMsgStatus;
> use Mail::SpamAssassin::PluginHandler;
>
> my $spamtest = new Mail::SpamAssassin({
> PREFIX => $PREFIX,
> DEF_RULES_DIR => $DEF_RULES_DIR,
> LOCAL_RULES_DIR => $LOCAL_RULES_DIR,
> LOCAL_STATE_DIR => $LOCAL_STATE_DIR,
> userprefs_filename => "$PREFIX/.spamassassin/user_prefs",
> userstate_dir => "$PREFIX/.spamassassin",
> debug => $debugLevel,
> local_tests_only => $local eq '1'
> });
>
> Is there anything obvious that causes this to fail?
>
> Why does the UPGRADE file start with
>
> Note for Users Upgrading to SpamAssassin 3.3.0