http://bugzilla.spamassassin.org/show_bug.cgi?id=4320
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Undefined |3.1.1
Version|3.0.3 |SVN Trunk (Latest Devel
| |Version)
------- Additional Comments From [EMAIL PROTECTED] 2005-07-06 21:58 -------
Triage: initial "version 0" reproduced here. DBM.pm error not reproduced.
> rm $HOME/.spamassassin/bayes*
> sa-learn --sync -D
output includes:
[6704] dbg: bayes: bayes journal sync starting
[6704] dbg: bayes: bayes journal sync completed
[6704] dbg: bayes: expiry starting
[6704] dbg: locker: safe_lock: created
/home/Bob/.spamassassin/bayes.lock.RoMe6.6704
[6704] dbg: locker: safe_lock: trying to get lock on
/home/Bob/.spamassassin/bayes with 0 retries
[6704] dbg: locker: safe_lock: link to /home/Bob/.spamassassin/bayes.lock: link
ok
[6704] dbg: bayes: tie-ing to DB file R/W /home/Bob/.spamassassin/bayes_toks
[6704] dbg: bayes: tie-ing to DB file R/W /home/Bob/.spamassassin/bayes_seen
[6704] dbg: bayes: found bayes db version 0
[6704] dbg: bayes: new db, set db version 3 and 0 tokens
[6704] dbg: locker: refresh_lock: refresh /home/Bob/.spamassassin/bayes.lock
[6704] dbg: bayes: DB expiry: tokens in DB: 0, Expiry max size: 150000, Oldest
atime: 0, Newest atime: 0, Last expire: 0, Current time: 1120711945
[6704] dbg: bayes: expiry completed
[6704] dbg: bayes: untie-ing
[6704] dbg: bayes: untie-ing db_toks
[6704] dbg: bayes: untie-ing db_seen
[6704] dbg: bayes: files locked, now unlocking lock
[6704] dbg: locker: safe_unlock: unlink /home/Bob/.spamassassin/bayes.lock
I can't tell whether it's because the DBM.pm problem is fixed in 3.1.0, or
whether my different prereq versions avoid the problem.
Regardless, it seems that "found bayes db version 0" is misleading.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
