Scott Ellentuch wrote on 10/04/24 5:15 am:
Apologies, but I don't understand.
I am running "make test" as the AWS user "ec2-user" when getting these
errors. Are you saying that its an acceptable error right now, and I can
just do the "sudo make install"?
If you ran "make test" as user "ec2-user", not "sudo make test" then I
misread this thread and looked at the wrong thing. The bug I found is an
unexpected problem when running the test as root even when home
directory permissions are relaxed.
Unless what happened was that you ran "sudo make test" and then tried
"make test" without deleting the files in the t/log directory that were
created owned by root by the "sudo make test", which would then cause
failures in the "make test".
To be clear: On a clean system that has everything needed by
SpamAssassin installed, running as user "ec2-user", you should be able
to run
perl Makefile.PL < /dev/null
make
make test
see no errors in the tests, and then run
sudo make install
If you are getting errors in spamd tests when running make test as
ec2-user then that might be indicating that something about the
configuration on aws regarding the network and access to ports is
getting in the way.
I don't know if there are any gotchas like that about setting up on aws,
but if there are, there are probably people on this mailing list who are
more familiar with any complexities in making a virtual machine on aws
properly configured to run SpamAssassin.
