I've just gone through an upgrade from a basic squeeze installation on
which sa-compile and sa-update had previously run successfully, and I
don't see the behavior you're talking about. Had you enabled the cron
job and run sa-compile successfully prior to the upgrade? My test system
is a virtual
On Tue, Jul 24, 2012 at 12:19:46AM -0700, Noah Meyerhans wrote:
Had you enabled the cron job and run sa-compile successfully prior to the
upgrade?
I don't remember. I had not touched the spamassassin setup for years.
My test system is a virtual machine on which only minimal packages were
severity 659474 normal
thanks
On Tue, Jul 24, 2012 at 11:30:25AM +0300, Antti-Juhani Kaijanaho wrote:
On Tue, Jul 24, 2012 at 12:19:46AM -0700, Noah Meyerhans wrote:
Had you enabled the cron job and run sa-compile successfully prior to the
upgrade?
I don't remember. I had not touched the
severity 659474 serious
tags 659474 + confirmed
thanks
I see the same problem in my squeeze - wheezy upgrade:
Preparing to replace spamassassin 3.3.1-1 (using
.../spamassassin_3.3.2-3_all.deb) ...
Stopping SpamAssassin Mail Filter Daemon: spamd.
Unpacking replacement spamassassin ...
[ ... lots
Package: spamassassin
Version: 3.3.2-2
Severity: normal
I recently upgraded from Squeeze to testing, and the spamassassin
upgrade (to version 3.3.2-2) didn't go smoothly. I have sa-compile
enabled.
I got the following error when dpkg tried to configure spamassassin:
Running sa-compile (may take
5 matches
Mail list logo
