Your message dated Sat, 2 Sep 2017 22:19:15 -0700
with message-id <[email protected]>
and subject line Re: Bug#308303: spamassassin: Error "bayes: bayes db version 0
is not able to be used, aborting!"
has caused the Debian Bug report #308303,
regarding spamassassin: Error "bayes: bayes db version 0 is not able to be
used, aborting!"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
308303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=308303
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: spamassassin
Version: 3.0.2-1
Severity: normal
I've used "sa-learn --ham --no-sync <file>" sequentially on several
messages, and for one of them, I got the following error:
bayes: bayes db version 0 is not able to be used, aborting! at
/usr/share/perl5/Mail/SpamAssassin/BayesStore/DBM.pm line 160.
This was done with a script, and here's the output:
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 0 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
bayes: bayes db version 0 is not able to be used, aborting! at
/usr/share/perl5/Mail/SpamAssassin/BayesStore/DBM.pm line 160.
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
Learned from 1 message(s) (1 message(s) examined).
[...]
This doesn't appear to be a db corruption, since I got no errors
for the following messages.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (900, 'testing'), (200, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.11
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Versions of packages spamassassin depends on:
ii debconf 1.4.30.13 Debian configuration management sy
ii libdigest-sha1-perl 2.10-1 NIST SHA-1 message digest algorith
ii libhtml-parser-perl 3.45-2 A collection of modules that parse
ii perl [libstorable-perl] 5.8.4-8 Larry Wall's Practical Extraction
ii spamc 3.0.2-1 Client for SpamAssassin spam filte
-- debconf information:
spamassassin/upgrade/2.40:
spamassassin/upgrade/2.40w:
spamassassin/upgrade/cancel: Continue
spamassassin/upgrade/2.42m: No
spamassassin/upgrade/2.42u: No
--- End Message ---
--- Begin Message ---
On Mon, May 09, 2005 at 11:17:45AM +0200, Vincent Lefevre wrote:
> I've used "sa-learn --ham --no-sync <file>" sequentially on several
> messages, and for one of them, I got the following error:
>
> bayes: bayes db version 0 is not able to be used, aborting! at
> /usr/share/perl5/Mail/SpamAssassin/BayesStore/DBM.pm line 160.
12 years pass...
It appears that this bug was fixed upstream in
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6901
As such, I am resolving it. Please don't hesitate to reopen if this is
still an issue.
noah
signature.asc
Description: PGP signature
--- End Message ---
