FYI, I opened and closed a ticket regarding this for proper tracking but
here's the main point.
The Apache SVN signature changed around 1/6/2011 (thanks Darxus for your
automated notifier).
Old fingerprint: CC:54:A4:A9:EC:3A:9B:1C:23:AC:2D:57:C6:96:9F:5F:4A:1D:2D:86
New fingerprint: BC:5F:40:92:FD:6A:49:AA:F8:B8:35:0D:ED:27:5E:A6:64:C1:7A:1B
This SVN update broke updatesd scripts. I don't believe it will break
anything else, though.
I believe I've updated the signature for that account on
spamassassin.zones.apache.org.
I'm now running these commands manually as updatesd to try and push out
a release:
bash /home/updatesd/svn/spamassassin/build/mkupdates/run_nightly
bash /home/updatesd/svn/spamassassin/build/mkupdates/run_part2
bash
/export/home/updatesd/svn/mkupdates-with-scores/do-stable-update-with-scores
I might need to run this twice because do-stable-update-with-scores
should run first, though, I think.
Here's how I resolved the svn issue for posterity.
Looking through all the cron output that I receive:
On spamassassin.zones.apache.org, I had to su - updatesd
cd /home/updatesd/svn/new-rule-score-gen
svn up
checked the key and hit p for store permanently
I believe this will then resolve all the scripts running under updatesd
that are getting stopped by interactive svn issues.
I also checked and the release account doesn't appear to use https for
svn so no changes needed there.
On spamassassin2.zones.apache.org, the nitemc account doesn't appear to
use https for svn so no changes needed there either.
I believe that should cover all the automated processes breaking rules
updates.
regards,
KAM
