On Wed, 3 Dec 2014, 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 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.
The rest has just been trying to figure out how to do that in a backwards-compatible manner.
-- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- You do not examine legislation in the light of the benefits it will convey if properly administered, but in the light of the wrongs it would do and the harms it would cause if improperly administered. -- Lyndon B. Johnson ----------------------------------------------------------------------- 11 days until Bill of Rights day
