From: Martin Langhoff Date: Thu, 31 Aug 2006 23:00:47 GMT Subject: Re: problem with git-cvsserver Message-ID: <46a038f90608311600p747c8a3anbe90dbac928e9923@mail.gmail.com> In-Reply-To: <20060831090333.GA28445@fiberbit.xs4all.nl> On 8/31/06, Marco Roeland wrote: > 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. Thanks for the info! I have to say though: Ouch. Do you know if there's an upgrade path for apps? Does v3 detect you've got a v2 file and do something smart (upgrade in place / spit out a readable error)? ... > I'd guess that you were unfortunate enough to just install some packages > during the transition Problem is that we have to help with the transition for users that started with v2 and get upgraded to v3 at the app level I suspect. > Incidentally I'd guess that in itself SQLite2 (so version 2) would also > function perfectly well for git-cvsserver (as would PostgreSQL or > MySQL) This was developed against v2. If v3 is backwards compatible, it'll just work. If not... we'll hear about it soon ;-) Pg/MySQL aren't really supported, though it wouldn't be that hard. martin