Bug#563325: need to run sa-update
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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563325: need to run sa-update
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 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 channel) at around the same time that the updated package hit volatile. In that case, sa-update is enough and you don't need to have installed the updated package at all. noah signature.asc Description: Digital signature
Bug#563325: need to run sa-update
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 channel) at around the same time that the updated package hit volatile. In that case, sa-update is enough and you don't need to have installed the updated package at all. Sorry for the lack of detail in my last mail, maybe I'm missing something and you can enlighten me. I'm using Spamassassin via amavisd-new, so after the installing the updated package from volatile I did the obvious /etc/init.d/amavis restart 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/3.002005/updates_spamassassin_org/72_active.cf ) new mails didn't get flagged as false-positive because of FH_DATE_PAST_20XX. Hmm, so why didn't upgrading the package and restarting amavisd-new do the trick all by itself? Kind regards Wolfgang Karall -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563325: need to run sa-update
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/3.002005/updates_spamassassin_org/72_active.cf ) new mails didn't get flagged as false-positive because of FH_DATE_PAST_20XX. 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. For people using sa-update, the updated packages were just about worthless, really. You still needed to install a local workaround (typically by disabling FH_DATE_PAST_20XX in local.cf) until sa-update pulled in the fix. But people wanted them... noah signature.asc Description: Digital signature
Bug#563325: need to run sa-update
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 shouldn't have been an issue. noah signature.asc Description: Digital signature
Bug#563325: need to run sa-update
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 clarification, I now realize what's the problem. Obviously I ran sa-update once (cronjob isn't enabled, and the timestamps on the files in the directory were way in the past) and hence the updated files in /usr/share/spamassassin were overruled by outdated ones. Basically this means either enable the daily cronjob or don't ever use sa-update at all, otherwise the system might get stuck with outdated rule files (even though there are newer ones installed by APT-provided packages). Anyway, thanks for the clear up and sorry for the noise. Kind regards Wolfgang Karall -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
