Processed: Re: Bug#659474: spamassassin: sa-compile problem on upgrade

2012-07-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 659474 normal Bug #659474 [spamassassin] spamassassin: sa-compile problem on upgrade Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 659474: http://bugs.debian.org/

Bug#659474: spamassassin: sa-compile problem on upgrade

2012-07-24 Thread Antti-Juhani Kaijanaho
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 touch

Bug#659474: spamassassin: sa-compile problem on upgrade

2012-07-24 Thread Antti-Juhani Kaijanaho
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 >

Bug#659474: spamassassin: sa-compile problem on upgrade

2012-07-24 Thread Noah Meyerhans
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 ma