Package: clive
Version: 0.4.11-1
Severity: normal

I installed the new clive version on my lenny system, but I was unable to run it. Is a depencency missing?

Many thanks,
Rainer

blackbox:~# aptitude install clive=0.4.11-1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done...

Twas brillig at 11:24:44 04.05.2008 UTC+02 when Rainer Dorsch did gyre and =
gimble:

Seems so. Does problem disapper after installing python-pysqlite2?

=2D-=20

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIHbJ1vse/O6JvVMgRAnNTAJ9q2R/j9T4zu4YSClqyvfoZenBTQACdEPC1
clTWBV+B4Ncj3xIvVAQvQes=
=pkL0
-----END PGP SIGNATURE-----

Rainer Dorsch wrote:

Try removing the ~/.clive/cache file. That column was added recently.
clive should have upgraded the cache file automagically, though.

What version of sqlite3 do you have installed?

Hi!

Stumbled into the same problem as Rainer, so I hope my feedback is
valueable, too.

On Sun, May 04, 2008 at 07:56:21PM +0700, Mikhail Gusarov wrote:

No, but that dependency is indeed missing.

On Sun, May 04, 2008 at 08:13:21PM +0300, Toni Gundogdu wrote:

Removing that file makes it indeed work again.

Doesn't seem to have happened, at least for Rainer and me.

Mikhail Gusarov wrote:

Gerfried Fuchs wrote:

Is the python2.5 package installed with the "sqlite3" module? That
module was not previously (<= 2.4) distributed with Python but had to be
installed separately (python-pysqlite2?). Apart from the difference how
these modules are being distributed, the only other difference that I am
aware of is how they are imported:

* import sqlite3 # This is what clive uses
* from pysqlite2 import dbapi2 as sqlite

So with this in mind I don't think that the python-pysqlite2 is
required. Perhaps someone who's more familiar with Debian Python
packages could give a better answer.

Gerfried Fuchs wrote:

I think that package depends on libsqlite3-0 (>= 3.4.2) so it's probably
safe to assume:

Twas brillig at 06:18:20 06.05.2008 UTC+03 when Toni Gundogdu did gyre and =
gimble:

Yes, and as python2.5 is now default python version in unstable,
dependencies are correct.

Won't you object if I temporarily add a kludge to Debian package which
removes cache file instead of upgrading it?

However, it depends whether upgrading cache went wrong or detecting that
upgrade is necessary.

=2D-=20

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

Mikhail Gusarov wrote:

I see no harm in doing that.

Remove the cache file if the error is raised? Sounds good to me. Less
hassle, too.

Just a follow up. I tried to reproduce this bug on systems with:
* sqlite-3.5.6; python-2.5.2
* sqlite-3.4.2; python-2.5.2

I used:
* clive-0.4.7
* clive-0.4.9

To create a database (~/.clive/cache) without the "cache_lowq" column
which was added in clive-0.4.10.

I then tried to get Python to raise the OperationalError with:
* clive-0.4.11

Which did not occur. clive-0.4.11 upgraded the database everytime as it
was supposed to.

I'll look into adding a safeguard for the OperationalError in
clive-0.4.12 which will cause clive to reset the cache automagically.