The masscheck portion of preparing the rules for publishing.
Is that hard to automate? If it has to be run once for
updates.spamassassin.org, is it difficult to run it twice?
[I really know very little about the back-end SA infrastructure.]
I guess you'd want to make sure that testing.updates included
everything that update does.
Well, once I get the current updates working, I'll let you know. ;-)
But I think it's svn credential related because I used svn to commit and
I think I removed a stored credentials and that's why updates are broken
at the moment.
Right now, I'm pretty much for least path of resistance to get stuff out
the door.
HOWEVER, here's a brilliant idea. We create an "ultrasafe" rule channel
or something like that. We put scores that disable the new RBL in that
and they can pull sa-update default + the ultrasafe channels and
combined they disable all new RBLs. Then masscheck remains as-is, etc.
Regards,
KAM
