Thanks., this appears to be the active.list error I was expecting. I've done an svn update and an svn revert on active.list.
If you can keep an eye out, we can see if that helps kick things in the butt. I had a feeling modifying active.list was going to break things. -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 On Tue, Jul 14, 2020 at 5:56 PM Giovanni Bechis <giova...@paclan.it> wrote: > The script ~/svn/nitemc/corpora_runs is executed on Saturday (automc > ~/svn/nitemc/corpora_runs >> ~/rsync/corpus/weekly-versions.txt) but I > think that last Saturday it failed in some way, last line of > weekly-versions.txt should contain the revision updated last Saturday > ("2020-07-11 1879784") but "svn info" gives revision 1879467. > "svn status --show-updates" tells that active.list is modified, I bet that > running "svn update" by hand will fail and some errors should be fixed by > hand. > I think that, as you wrote, you should login, sudo to automc, svn up and > then fix svn errors to be able to update the tree to latest revision. > > Regards > Giovanni > > On 7/14/20 3:25 PM, Kevin A. McGrail wrote: > > GB: I hadn't looked at masscheck as been sidetracked. Henrik pointed > out we fixed the lint warning issue on sa-update back with 3.4.3 so the > people opening bugs are running old versions. This isn't the lint issue, > this is _check_whiitelist which is an internal function. I fixed that on > the 10th in revision 1879735 < > https://svn.apache.org/viewvc?view=rev&rev=1879735> > > > > From Memory, I think that SA will use the same version of the code for a > week for masschecks but that could be an old system. > > > > Not sure if kicking the svn checkout. Should I login, sudo to automc > and go to /usr/local/spamassassin/svn/trunk and do svn up? It's definitely > running an older version from the 3rd, I checked on the server myself. > > > > > > Hege: Thanks. References to KAM's crashplan are out of date. PCCC > donates Crashplan services to the project / ASF formally since Spring > 2018. It's the project's crashplan and the credentials encrypted are > stored in https://svn.apache.org/repos/asf/spamassassin/sysadmins/accounts > so that two people had the credentials. > > > > Suggest you archive that 2017 Wiki Page and copy it to a new > InfraNotes2020. Then you can rip and shred without any concerns. > > > > Regards, > > KAM > > > > -- > > Kevin A. McGrail > > Member, Apache Software Foundation > > Chair Emeritus Apache SpamAssassin Project > > https://www.linkedin.com/in/kmcgrail - 703.798.0171 > > > > > > On Tue, Jul 14, 2020 at 8:23 AM Henrik K <h...@hege.li <mailto: > h...@hege.li>> wrote: > > > > On Tue, Jul 14, 2020 at 02:20:29PM +0200, Giovanni Bechis wrote: > > > > > > automc seems still broken atm (commit to active.list fails), I am > pretty sure you are aware of it and it will be fixed on new vm. > > > I do not want to touch sa-vm1 now, new vm could go out-of-sync. > > > https://markmail.org/message/ijg75xj3mguzvaxa > > > > Nothing can go out-of-sync. At the time of switchover, all > processes/crons > > are stopped and final rsync is made to new vm. > > > >
