Re: version.h.pl show stopper
It turns out that spamassassin is depending on risky behavior, https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1238 I have submitted a patch, https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7367 .
Re: How to use BUILD_SPAMC=no ?
I see. Submitted https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7376
How to use BUILD_SPAMC=no ?
In Makefile.PL we observe 'BUILD_SPAMC' ,# Set to 'no' to skip build of spamc. 'BUILD_SPAMD', # Set to 'no' to skip build of spamd. Does this mean we can do perl Makefile.PL BUILD_SPAMC=no BUILD_SPAMD=no ? But if I see cd spamc /usr/bin/perl version.h.pl in the compilation, does that mean I have made a mistake?
Re: version.h.pl show stopper
You people were right about $ mount|grep noexec And the tests really should check for that. I'll submit a bug. That apparently was the problem on one of my machines. But for all the rest, this still fails: env - HOME=$HOME LOGNAME=$LOGNAME PATH=/usr/bin:/bin USER=$USER sh -uxe
Re: version.h.pl show stopper
Sure, it exists $ find -name version.h.pl -ls 432321 4 -rwxr-xr-x 1 jidanni jidanni 1107 Nov 19 09:19 ./spamc/version.h.pl but that doesn't help anything.
version.h.pl show stopper
$ svn checkout http://svn.apache.org/repos/asf/spamassassin/trunk /tmp/ee $ cd /tmp/ee $ echo|perl Makefile.PL PREFIX=/tmp/g $ make In the end you will see cd spamc /usr/bin/perl version.h.pl spamc/configure.pl: Can't exec `version.h.pl': No such file or directory at spamc/configure.pl line 74. Makefile:1812: recipe for target 'spamc/Makefile' failed make: *** [spamc/Makefile] Error 2 No?
Unable to parse URL powered by spamassassin.psd
Help, on some of my machines I constantly get $ svn update Arulesrc/sandbox/jquinn Arulesrc/sandbox/jquinn/20_misc.cf Urulesrc/scores/scores-set0 Urulesrc/scores/stats-set0 Urulesrc/scores/scores-set1 Urulesrc/scores/stats-set1 Urulesrc/scores/scores-set2 Urulesrc/scores/scores-set3 Urulesrc/scores/72_scores.cf svn: Unable to parse URL '/repos/asf/!svn/bc/1673327/spamassassin/trunk/powered_by/powered by spamassassin.psd' On others things go fine. I am not the owner of svn on some of the machines, so cannot update it if that is the issue. Please use more conservative file names if that is the issue.