You'll love this..
My nightly sa-update cron ran last night and upgraded my modified
rules (was version 916621) to a newer version (version 917420). This, of
course, undid my changes. And equally surprising, --lint passed.
I looked at the diffs and sure enough, the same lines were back (number
Karsten Bräckelmann wrote:
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
On Mon, 2010-03-01 at 06:45 -0500, Lee Dilkie wrote:
Karsten Bräckelmann wrote:
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?
I was originally running the 3.3 rules and that was fine, and as far
no joy.
doesn't look like the ports version of SA comes with any stock rules
(nothing obvious in the ports dir tree, the work/ directory had en empty
72_active.cf file)... I deinstalled and then installed and it all went
well but it tells me to run sa-update to get the rules, and that's my
progress report.. commented out the place where the lint results were
checked and rules got installed.
looking at 72_active.cf I see a number of lines ending in CR (^M). Is
this intentional?
ie.
header __SUBJ_3DIGIT Subject =~ /\b\d{3}[^0-9]/^M
header __SUBJ_APPROVE
Final update folks, sorry for the noise if it's bothersome...
commented out the three offending lines in 72_active.cf and --lint
passed and I'm back up and running.
No idea what the issue is, those lines looked fine to me. I'm running
perl 5.8.9, could that be an issue?
-lee
details: ##lee is
Folks,
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.
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
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.
