Or creating it in a temporary location knowing it will be changed later. -- Kevin A. McGrail Asst. Treasurer & VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Tue, Mar 20, 2018 at 2:45 PM, Bill Cole < sa-bugz-20080...@billmail.scconsult.com> wrote: > On 20 Mar 2018, at 14:19, Kevin A. McGrail wrote: > > That is an interesting question because you are right, they are supposed to >> be immutable. Dave, is something happening in an 18 hour window as he >> describes? >> > > > I'm not Dave, but I can see that interval in commit messages. Times are > UTC-4: > > From: spamassassin_r...@apache.org > To: comm...@spamassassin.apache.org > Subject: svn commit: r1827165 - /spamassassin/tags/sa-update_3 > .4.2_20180319083200/ > Date: March 19, 2018 at 4:34 AM > Author: spamassassin_role > Date: Mon Mar 19 08:34:51 2018 > New Revision: 1827165 > > URL: http://svn.apache.org/viewvc?rev=1827165&view=rev > Log: > promotions validated > > Added: > spamassassin/tags/sa-update_3.4.2_20180319083200/ > - copied from r1827164, spamassassin/trunk/ > ============================================================ > ========================== > From: spamassassin_r...@apache.org > To: comm...@spamassassin.apache.org > Subject: svn commit: r1827256 - in /spamassassin/trunk/rulesrc/scores: > 72_scores.cf scores-set0 scores-set1 scores-set2 scores-set3 stats-set0 > stats-set1 > Date: March 19, 2018 at 10:41 PM > Author: spamassassin_role > Date: Tue Mar 20 02:41:21 2018 > New Revision: 1827256 > > URL: http://svn.apache.org/viewvc?rev=1827256&view=rev > Log: > updated scores for revision 1827165 active rules added since last > mass-check > > Modified: > spamassassin/trunk/rulesrc/scores/72_scores.cf > spamassassin/trunk/rulesrc/scores/scores-set0 > spamassassin/trunk/rulesrc/scores/scores-set1 > spamassassin/trunk/rulesrc/scores/scores-set2 > spamassassin/trunk/rulesrc/scores/scores-set3 > spamassassin/trunk/rulesrc/scores/stats-set0 > spamassassin/trunk/rulesrc/scores/stats-set1 > > Modified: spamassassin/trunk/rulesrc/scores/72_scores.cf > > ============================================================ > ========================== > > > These seem to be ultimately caused by the cron jobs for run_nightly (which > creates an update fileset) and do-stable-update-with-scores, which calls > mkupdate-with-scores (which ALSO creates an update fileset.) > > > There is a design problem here. I am guessing that run_nightly should NOT > be generating an update fileset, since it seems that a fileset with proper > scores for those rules is being created 18 hours later. > > > >
