On Sun, 2010-01-03 at 12:04 -0500, Noah Meyerhans wrote:
> > Hmm, so why didn't upgrading the package and restarting amavisd-new do
> > the trick all by itself?
>
> Because the updates, in /var/lib/spamassassin/3.002005/, override the
> rules in /usr/share/spamassassin.
OK, thanks for the clarifi
I should also point out that, had updates.spamassassin.org carried the
fixed rule a couple days earlier, it's very likely that nobody would
have noticed this problem, and there wouldn't have been any call to
produce updated packages. Given that the bug was known upstream months
ago, it really shou
On Sun, Jan 03, 2010 at 05:26:36PM +0100, Wolfgang Karall wrote:
> but still got mails flagged with FH_DATE_PAST_20XX. At that time the
> file /usr/share/spamassassin/72_active.cf already had the updated regex,
> but only once I ran sa-update (which also updated the file
> in /var/lib/spamassassin/
On Sun, 2010-01-03 at 10:08 -0500, Noah Meyerhans wrote:
> No, you don't need to run sa-update at all. The package contained the
> necessary fix.
>
> If you're using sa-update, via cron or otherwise, then the fix was
> available to you via sa-update (from updates.spamassassin.org, the
> default c
On Sun, Jan 03, 2010 at 09:43:23AM +0100, Wolfgang Karall wrote:
> I'd like to point out that I had to run sa-update manually after
> updating the package from volatile, it would've been nice if that was
> mentioned in the VUA mail.
No, you don't need to run sa-update at all. The package containe
Hi,
I'd like to point out that I had to run sa-update manually after
updating the package from volatile, it would've been nice if that was
mentioned in the VUA mail.
Kind regards
Wolfgang Karall
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe"
6 matches
Mail list logo
