corrected md5sums for bogofilter-0.94.6
David Relson
relson at osagesoftware.com
Wed Apr 27 13:33:16 CEST 2005
G'day,
Due to a problem (described below) with my build environment, the
binary rpms initially released yesterday were bad. Unfortunately I
discovered that shortly after sending out the announcement.
The problem has been corrected and new files were uploaded to
sourceforge. For your convenience here are the correct md5sums:
6c4fd412ae5a9563a1986cc8504f615e bogofilter-0.94.6-1.i586.rpm
233926fe470445cdef3216c160f24679 bogofilter-0.94.6-1.src.rpm
8213091e0e3f770b7eeeadea14e04e87 bogofilter-0.94.6.tar.bz2
953ccdf7151dd8f93ba8cf6e946867e8 bogofilter-0.94.6.tar.gz
cae97aa4f692957a409cb03eba5fac39 bogofilter-static-0.94.6-1.i586.rpm
Note: the problem files were uploaded to sourceforge yesterday around
23:15 GMT and the corrected files were uploaded approx 23:45 GMT
Regards,
David
### problem description ###
The rpm build process, i.e. "make rpm" starts in my bogofilter
development directory. Due to some previous bogofilter experiments
there was a DB_CONFIG file in that directory. rpm opens the file and
gets confused.
Here's how I reproduce the problem:
[relson at osage tmp]$ rpm -qf /bin/bash
bash-3.0-2mdk
[relson at osage tmp]$ echo set_flags DB_LOG_AUTOREMOVE > DB_CONFIG
[relson at osage tmp]$ rpm -qf /bin/bash
error: cannot open Basenames index using db3 - Invalid argument (22)
error: cannot open Providename index using db3 - Invalid argument (22)
file /bin/bash is not owned by any package
More information about the Bogofilter-announce
mailing list