Bugzilla Bug 146079

When I upgraded from popfile 0.20.1 to 0.22.4 (yes, this is a long delay in
reporting) I got bit after my next reboot complained that it could not find
SQLite (Perl module).  There is a dependency for dev-perl/DBD-SQLite2, but not
for SQLite.  However, the script only uses SQLite2 if the version of SQLite is
above some cutoff - but that means it fails if it can't fine it at all.  It was
easy for me to just emerge SQLite, but this should either be added to the
dependencies or the script should just go to SQLite2 if it can't find SQLite
and not fail.

Hi,

Thanks for reporting this.  Just to be clear - which package did you merge to
get around this?

Best regards,
Stu

Stu,

Sorry - but I was SURE I responded to this over a week ago.  I've probably got
a response posted to some completely unrelated bug....

I believe what I emerged was dev-perl/DBD-SQLite.  I just spent some time
looking at the scripts, and I think I was probably barking up the wrong tree. 
It looks like all that is needed is to change popfile.cfg to have
"bayes_dbconnect dbi:SQLite2:dbname=$dbname" (instead of SQLite).  However, it
looks like that file is not included in the ebuild, but gets built on the fly
if it doesn't exist.  I can't find where that parameter gets its default value,
but if you can change that, then the dependencies are probably OK.

net-mail - someone interested in taking this package? Stuart is retired... :/

Well, I've just done a reinstall due to a dead disk, and the problem still
exists.  However, it looks like an easy solution (I can't tell if it's really
the best or if it would break anything elst) is to change the 'dbconnect' value
on line 220 of Classifier/Bayes.pm (under the popfile main directory) from
'dbi:SQLite:dbname=$dbname' to 'dbi:SQLite2:dbname=$dbname'.

The ebuild requires dev-perl/DBD-SQLIte2, but the package actually tries to run
DBD:SQLite first, and if the version is too high (and therefore using an
incompatible version of the underlying SQLite database) it only then tries to
use DBD:SQLite2.  Changing the default dbconnect value bypasses this problem.

I've added 0.22.5 to tree, was there something else that needed to be done to
close this? It defaults to SQLITE2 afaik.