On Sun, 2010-02-28 at 18:44 -0500, Lee Dilkie wrote:
> For what ever reason, my sa-update to 3.30 has buggered itself. In my
> efforts to debug it's now at the situation that SA has no rules to run
> and I'm getting swamped.
The first sentence is seriously confusing. You can not "sa-update to
3.3.0". sa-update only updates the rules, for the already installed
version.
> How, if it's possible, can I tell SA and sa-update to use the 3.2
> version of the ruleset? Simply deleting the tree and sa-compiling did
> not work. SA is still looking for 3.3 rules and as it finds none, is
> letting everything through.
You cannot really and reliably make SA 3.3 use 3.2 rules.
Anyway, what comes to mind: Did you run sa-update after the upgrade to
3.3.0 at all? If not, did you install the rules tarball alongside SA?
How did you upgrade? Any chance both versions ended up living on your
system?
Running 3.3.0 with a broken sa-update for whatever reason, can be cured
by removing the entire update dir, and installing the plain, stock 3.3.0
rules tarball, if not already done.
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
