John Hardin wrote: > Bob Proulx wrote: > > There have been multiple facets to this problem. The first was a rule > > update that produced warnings that produced email from every cron run > > sa-update / sa-learn run if run on recent released spamassassin 3.4.0 > > but not the development trunk version. > > That was actually the second facet. The first facet was a new test rule > using a perl RE syntax that was introduced in 5.10.0 This rule passed dev > validation on perl 5.18-ish, ...
But, but, but... It also failed lint and produced cron noise on my perl 5.20.1 system too. Running spamassassin 3.4.0. That is later than perl 5.18 and it definitely produced the warning message. It couldn't have been solely due to perl version or there wouldn't have been any warnings there. It could only have been due to the spamassassin version 3.4.0, the latest released version, which did not include the development trunk code. > but when it was installed by sa-update on a production 5.8.8-based > install it failed lint and the entire rules update was > rejected. Avoiding that was the impetus for being able to test the > version of perl in a SA conditional. AIUI the combination of versions there is RHEL5/CentOS5 with perl 5.8.8 and spamassassin 3.3.1. Apparently there it is the perl 5.8.8 that tickled a problem because 3.3.2 with perl 5.14 is okay. > The rest has just been trying to figure out how to do that in a > backwards-compatible manner. Yep. The devil is in the details! Bob
