http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4788
------- Additional Comments From [EMAIL PROTECTED] 2006-03-10 00:18 ------- (In reply to comment #29) > > Also (after sa-update is run): > > The only header added to processed mail is: X-Spam-Checker-Version > > Not good. > > Of course that's because there's nothing in /var/lib/spamassassin/3.001001/ > yet. > > *smacks head* > > So... I'm +1 on 3405 assuming that the 3.1.1 update channel is setup before > release of 3.1.1. :) Two things: 1) the update channel doesn't actually need to be setup -- if there are no updates available, sa-update doesn't create the directories and there's no problem. but yes, the full ruleset needs to be available once we start. I've already got a working area (https://svn.apache.org/repos/asf/spamassassin/rules/ branches/3.1) which is manually modified to get an update released. 2) I didn't think about it when the changes were being made to sa-update recently, but the new way of doing things (use local_state_dir for all rules) instead of using sa-update for just updates to rules in released versions means that people *have* to use sa-update for updates.sa.org if they want to use any channels at all. I think this isn't terrible for 3.1, but we'll want to think more about this for 3.2. I'll make another ticket to discuss it. BTW: I changed the sa.kluge.net channel to have the full (current) 3.1 rule distribution, so it should actually function like it would "in the real world" ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
