On 6 May 2015, at 20:57, Kevin A. McGrail wrote:

Hello SpamAssassin Users and Developers,

I wanted to take a moment to provide my $0.02 on two in the wild issues with 3.4.1 that I've heard a lot about in the past few days:

The first in the wild issue has been some failures on sa_compile.t. These errors are confirmed as solely test errors and do not indicate an issue with using compiled rules in production. You can see more about the issue on https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7181 and https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7005. If you are affected by this issue, an easy work around is to rename the re2c executable during cpan installations or make tests so that the sa_compile.t test is skipped.

I would (for obvious reasons) add to that list https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7188 which is also worked around by skipping the test OR by applying the patch attached to the bug. It appears that this bug has been around a long time and went unnoticed because the bulk of people using /opt/$DIR as a prefix for build/test are MacPorts users and MacPorts doesn't run tests by default or ever test as root, so the most serious risk (damaging the operational rule & config directories under /{etc,var}/opt/) is avoided.

As with the other sa_compile.t issue, I don't see that as any sort of emergency issue. The tests implemented in that file are more for developers than for end-users in that they answer "is rule compilation broken in general?" without answering "is my build able to compile rules?"

Reply via email to