On Fri, Oct 24, 2003 at 03:16:15AM +0300, Juha Nieminen wrote: > here has done something to the system-wide perl installation (which I > doubt because SpamAssassin uses a fixed path to the perl installation > directory which has a version number in it, and I doubt that anyone > would go change that; a new version of perl would go to a differently > named directory), I don't know why this phenomenon is happening.
it's not the perl version that's the issue, it's the modules that perl uses. but if you're running a 2.60 devel version, all bets are off. > It *could* perhaps be that there was a bug in 2.60-cvs and now the > databases are broken? it could very well be. > % spamassassin --version > SpamAssassin version 2.60 > > Before using the version 2.60-cvs I used the 2.5* version, and that > file is probably a remnant of that, in that case, if you run sa-learn with -D, you should see it try to do the upgrade, the error happens, and the upgrade fails. > Since I can't make system-wide installations in this system, if SA > needs some newer version of DB_File, how do I make a local installation? I'm not sure if you can actually. you may want to move the current dbs aside, and see if you can make a new db with sa-learn. if it works, I'd just build a new one. if it doesn't, I'd either talk to your admins, or disable bayes. -- Randomly Generated Tagline: If this were Ada, we'd simply doc it as "erroneous". -- Larry Wall in <[EMAIL PROTECTED]>
pgp00000.pgp
Description: PGP signature