On 2024-01-29 at 23:06:07 UTC-0500 (Tue, 30 Jan 2024 14:06:07 +1000)
Nick Edwards <nick.z.edwa...@gmail.com>
is rumored to have said:
omfg
even killing it, then having to kill every individual sub process
manually...
re run using -f
and it still loops and times out.
very braindead install process. looks like there is no way for
spamassassin to install, I never recall having this problem ever
before on
all 3.x versions, but 4.0.0 is a useless bitch, i'm about to install
rspamd
I'm sorry to hear that you're having such problems. I don't know of any
major changes to the install process in 4.x, so without any specific
details I can't really offer a solution.
I can say that AS ALWAYS it is a bad idea to build and test ANY software
as 'root' and SA does not accommodate doing so. There may well be places
where the tests fail slowly if you run them as root. The only step you
should perform as root is the actual installation. Another possible
issue arising from how some platforms (e.g. RedHat) use Perl's
"local::lib" mechanism by default, giving each user their own bespoke
Perl environment. You must disable that when building and testing SA.
I'm not sure how exactly one should use the cpan tool to install SA or
any other Perl package designed as a system-wide facility. I think it is
generally better to either use distro-provided packages or to do the
real install from source with this arcane spell:
perl Makefile.PL
make build && make test
sudo make install
On Tue, Jan 30, 2024 at 1:36 PM Nick Edwards
<nick.z.edwa...@gmail.com>
wrote:
Venting
Set up a new server today, took no time in postfix dovecot and
amavisd,
apache roundcube, and everything, then came spamassassin
thankfully I chose to install this whilst we left for lunch, but
45mins
later to my horror it was still trying to install, why? because its
tests
failed for timeouts this, timeouts that, everytime its set keeps on
retrying reporting
error: config: no rules were found! Do you need to run 'sa-update'?
config: no rules were found! Do you need to run 'sa-update'?
of fricken course there is no rules, its a new fricken install that
cpan
hasn't got around to yet to allow us to run sa-update.
perhaps spamassassin developers can consider not everyone is
upgrading,
there are some of us trying to get the fricken thing on the fricken
machine
in the fricken first place.
I am not going to run cpan with force because that may hide *real*
errors.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
