Re: problem with git-cvsserver

From: Marco Roeland <marco.roeland@xs4all.nl>
Date: Aug 31, 2006, 09:03 UTC
Message-ID: <20060831090333.GA28445@fiberbit.xs4all.nl>
In-Reply-To: <46a038f90608301329n14df4dd2tb1563cc48662cd14@mail.gmail.com>

On Thursday August 31st 2006 at 08:29 uur Martin Langhoff wrote:

Show 6 quoted lines

> [git-cvsserver and trouble with Perl DBI and SQLite]
> 
> Actually, just looking at my etch dev box, libdbd-sqlite-perl is
> 0.29-1 and sqlite is 2.8.16-1. Not sure if the difference is
> significant. Perhaps SQLite v3 has a different invocation / driver
> name?

Yes, SQLite v2 and SQLite v3 are different and binary incompatible.

However, on Debian 'etch' you can install packages for both versions concurrently; most packages for SQLite have either a '2' or a '3' in the name. Packages without the number use the "best current choice" which is "3" in 'etch' at the moment but was "2" not too long ago.

So at this moment in Debian 'etch' SQLite3 is the default version and calling

        my $dsn = 'dbi:SQLite:dbname=foo';

will use the SQLite3 driver internally, for which you must have installed the "libdbd-sqlite3-perl" package. Just for the record, if you'd wanted the older SQLite2 version you would install the "libdbd-sqlite2-perl" package and from Perl call "my $dsn = 'dbi:SQLite2:dbname=foo';".

I'd guess that you were unfortunate enough to just install some packages during the transition and now some parts look for the "2" version and other parts for the "3" version. Probably just installing the "libdbd-sqlite3-perl" package and upgrading the other sqlite packages (from synaptic say to easily find them!) will probably cure your situation.

Incidentally I'd guess that in itself SQLite2 (so version 2) would also function perfectly well for git-cvsserver (as would PostgreSQL or MySQL), it's probably in this case just a slight version skew between packages!

-- 
Marco Roeland