git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: problem with git-cvsserver

From
Aaonghus <thecolourblue@gmail.com>
Date
Aug 31, 2006, 12:04 UTC
Message-ID
<44F6D064.9020002@gmail.com>
In-Reply-To
<20060831090333.GA28445@fiberbit.xs4all.nl>
Marco Roeland wrote:
Show 40 quoted lines
> On Thursday August 31st 2006 at 08:29 uur Martin Langhoff wrote:
>
>   
>> [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!
>   
Hi,
Thanks for all the help- I have it working now. It was not a fault with 
git-cvsserver at all- more like my own stupidity. The problem was that I 
had checked the versions on my client machine and forgotten to update 
the cvs/git server! Once I updated it and installed the 
libdbd-sqlite3-perl package (on the server) everything works as expected.
 
So, just to confirm, git-cvsserver is working on a debian 
testing/unstable machine (acting cvs/git server) with the following 
versions:
    libdbd-sqlite3-perl (1.12-1)
    libdbi-perl (1.51-2)
    libsqlite3-0 (3.3.7-1)
    perl (5.8.8-6.1)
    perl-base (5.8.8-6.1)

Apologies for wasting your time, looks like my caffeine levels are getting dangerously low...

a
 
Previous: Marco RoelandNext: Martin Langhoff
Message 7 of 11 in “problem with git-cvsserver”
  1. aonghusAug 30, 2006
  2. Johannes SchindelinAug 30, 2006
  3. aonghusAug 30, 2006
  4. Junio C HamanoAug 30, 2006
  5. Martin LanghoffAug 30, 2006
  6. Marco RoelandAug 31, 2006
  7. aonghusAug 31, 2006
  8. Martin LanghoffAug 31, 2006
  9. Johannes SchindelinAug 31, 2006
  10. Martin LanghoffSep 1, 2006
  11. Marco RoelandSep 1, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.