Bug#739489: spamassassin: Failed to update

2018-09-30 Thread Noah Meyerhans
On Sun, Feb 23, 2014 at 07:05:29PM -0700, Bob Proulx wrote: > Best would be if spamassassin itself was able to understand that this > directory is not fully populated yet and ignore it until it is so that > it could avoid the "no rules" error itself. If there is a bug to be > pointed at I think th

Bug#739489: spamassassin: Failed to update

2014-02-26 Thread Stefano Callegari
Il Tue, Feb 25, 2014 at 09:39:09AM +0100, To Noah Meyerhans scrisse: > Il Sun, Feb 23, 2014 at 07:48:29PM -0500, Noah Meyerhans scrisse: > [cut] > > If you delete /var/lib/spamassassin/3.004000, you should be able to > > update to 3.4.0. Can you confirm this? If that works, then I'd be > > I confi

Bug#739489: spamassassin: Failed to update

2014-02-25 Thread Stefano Callegari
Il Sun, Feb 23, 2014 at 07:48:29PM -0500, Noah Meyerhans scrisse: [cut] > If you delete /var/lib/spamassassin/3.004000, you should be able to > update to 3.4.0. Can you confirm this? If that works, then I'd be I confirm. > interested in seeing if things stay stable following a manual run of > sa-

Bug#739489: spamassassin: Failed to update

2014-02-23 Thread Bob Proulx
Noah Meyerhans wrote: > If bug 739373 was triggered on the first sa-update run, then > /var/lib/spamassassin/3.004000 would have been created but never > populated with rules. This could leave spamassassin in a situation > similar to the one you're in. It would have to affect the very first run > o

Bug#739489: spamassassin: Failed to update

2014-02-23 Thread Noah Meyerhans
On Fri, Feb 21, 2014 at 09:46:13AM +0100, Stefano Callegari wrote: > Feb 21 09:12:22.731 [22110] dbg: config: using > "/var/lib/spamassassin/3.004000" for sys rules pre files > Feb 21 09:12:22.731 [22110] dbg: config: using > "/var/lib/spamassassin/3.004000" for default rules dir > Feb 21 09:12:22.

Bug#739489: spamassassin: Failed to update

2014-02-21 Thread Stefano Callegari
Il gio, feb 20, 2014 at 10:18:47 +0100, To Noah Meyerhans scrisse: [cut] > and no more errors! > > /var/cache/apt/archives <-su> # /etc/init.d/amavis status > [ ok ] amavisd is running. > > gio feb 20 09:51:32 @hpdv5: > /var/cache/apt/archives <-su> # /etc/init.d/spamassassin status > [ ok ] spa

Bug#739489: spamassassin: Failed to update

2014-02-20 Thread Stefano Callegari
Il Thu, Feb 20, 2014 at 12:36:38AM -0500, Noah Meyerhans scrisse: > On Wed, Feb 19, 2014 at 10:32:15AM +0100, Stefano wrote: > > Feb 19 09:27:30 hpdv5 spamd[29307]: logger: removing stderr method > > Feb 19 09:27:30 hpdv5 spamd[29310]: config: no rules were found! Do you > > need to run 'sa-update'

Bug#739489: spamassassin: Failed to update

2014-02-19 Thread Noah Meyerhans
On Wed, Feb 19, 2014 at 10:32:15AM +0100, Stefano wrote: > Feb 19 09:27:30 hpdv5 spamd[29307]: logger: removing stderr method > Feb 19 09:27:30 hpdv5 spamd[29310]: config: no rules were found! Do you > need to run 'sa-update'? That's odd, since of course there are rules included in the package. Ha

Bug#739489: spamassassin: Failed to update

2014-02-19 Thread Stefano
Package: spamassassin Version: 3.4.0-1 Severity: important Tags: d-i Dear Maintainer, during last update, aptitude exit with Failed to perform requested operation on package. Trying to recover: Configurazione di spamassassin (3.4.0-1)... Starting SpamAssassin Mail Filter Daemon: child process [