Micah Anderson wrote:
> The original bug report said that you were running:
> 
> Version: 0.93.1-1
> ii  libdb4.2                    4.2.52-17    Berkeley v4.2 Database Libraries
> 
> and your problem occurs with both:
> bogofilter_0.93.3.1-1_i386.deb
> bogofilter_0.93.5-1_i386.deb
> 
> You say that bogofilter_0.93.1-1_i386.deb works and then go on to say:
> 
> "At least bogofilter_0.93.1-1_i386.deb or the one before works without 
> crashing the db file."
> 

The version number was wrong because I had already rolled it back to 
93.1-1 The bug refers to 93.5-1 (and 93.3.1-1)

> This is because your log format needs to be updated to the new format,
> as the NEWS.Debian file indicates. 

I deleted and recreated the db files before I ran with the upgrade.


> Version 0.93.1 depended on libdb
> 4.2.25 (as you correctly have in the original report), moving to
> 0.93.0-2 or anything newer requires you to upgrade your libdb to 4.3
> and perform the NEWS.Debian log format change procedure. 

I had and still have installed:
ii  libdb1-compat  2.1.3-7        The Berkeley database routines [glibc 
2.0/2.
ii  libdb3         3.2.9-20       Berkeley v3 Database Libraries [runtime]
ii  libdb3-dev     3.2.9-20       Berkeley v3 Database Libraries 
[development]
ii  libdb4.2       4.2.52-17      Berkeley v4.2 Database Libraries [runtime]
ii  libdb4.3       4.3.27-1       Berkeley v4.3 Database Libraries [runtime]

My understanding is that these do not conflict (if so this is a 
dependency issue).
  > I suggest that you either go through the more painful proceedure of
> dumping your wordlists to .txt files, destroying your DB environments
> and then recreating them by reloading your wordlist.txt files, or
> follow the steps outlined in the NEWS.Debian to upgrade your wordlist
> databases. 

I deleted and recreated the db files.

> 
> I am fairly confident that you will then find that your problem no
> longer exists, as this is exactly what I had to do to make the problem
> go away.

The problem exists after recreating all new db and log files via 
bogofilter. (I archive all ham AND spam). It only appeared after about 
48 hours of operation (the wrong version fails right away).

I don't see how this problem can be related to a change in db files when 
they were created after the upgrade.

If bogofilter is using the wrong version of libdb that is not because 
old db files because I deleted and recreated them.

For the record -The only lines from a grep db /etc/bogofilter.cf  are 
commented out just as in the default.

###wordlist i,ignore,~/ignorelist.db,1
###wordlist r,wordlist,~/wordlist.db,2
##db_cachesize=0
###db_cachesize=16
##      If you run out of locks, see file README.db,
##db_lk_max_locks=16384
##db_lk_max_objects=16384




----------------------------------------------------------------
Karl Schmidt                         EMail <email address hidden>
Transtronics, Inc.    		       WEB http://xtronics.com
3209 West 9th Street                    Ph (785) 841-3089
Lawrence, KS 66049                     FAX (785) 841-0434


"Even if you are on the right track,
you'll get run over if you just sit there" - Will Rogers
----------------------------------------------------------------