You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by si...@apache.org on 2022/12/06 20:56:14 UTC

svn commit: r1905814 - /spamassassin/trunk/build/README

Author: sidney
Date: Tue Dec  6 20:56:14 2022
New Revision: 1905814

URL: http://svn.apache.org/viewvc?rev=1905814&view=rev
Log:
Minor edit to release build instructions documentation

Modified:
    spamassassin/trunk/build/README

Modified: spamassassin/trunk/build/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/README?rev=1905814&r1=1905813&r2=1905814&view=diff
==============================================================================
--- spamassassin/trunk/build/README (original)
+++ spamassassin/trunk/build/README Tue Dec  6 20:56:14 2022
@@ -213,13 +213,17 @@ Run "svn status" to ensure you're buildi
   information on how to set up to run the sawampersand test.
 
 - Run the tests that require sudo privileges. DO NOT run these on a machine that
-  runs a production copy of SpamAssassin.
+  runs a production copy of SpamAssassin. As a precaution these tests require that
+  you edit t/config.dist to set run_root_tests to y. Also, these tests run some
+  processes as user 'nobody' and must be run in a directory that is accessible. Typical
+  linux systems give no permissions for "other" on home directory trees. You will
+  have to change the permissions or run these tests from within a different directory.
 
     sudo make test TEST_FILES="t/root*.t"
 
 - Check in the updated Changes file, and SpamAssassin.pm.
 
-    svn commit -m "preparing to release X.Y.Z"
+    svn commit -m "preparing to release X.Y.Z" Changes lib/Mail/SpamAssassin.pm
 
   (If you are privately preparing a security release, and don't wish to
   perform commits to public SVN repos, you can defer this step until