On Mon, 2006-05-01 at 13:25 +0100, Max Bowsher wrote: > $ apt-cache show python2.3-pysqlite2 > Package: python2.3-pysqlite2 > ... > Depends: libc6 (>= 2.3.5-1), libsqlite3-0 (>= 3.3.5), python2.3 > ... > > As you can see, there *is* a dependency on sqlite. Uh, my mistake. I have checked it, but somehow could not recognise that it has an sqlite3 dependency. :-(
> I was a little unclear, though - I referred to the sqlite3 source > package without considering which of the generated binary packages > should actually have the 'Conflicts'. It was not a problem, but I did overlook the python-pysqlite2 dependency line, my mistake. > It would need to be the > 'libsqlite3-0' binary package, not the 'sqlite3' binary package. Still, this dependency is solved from python-pysqlite2, but yes, not yet from python-sqlite. As the former in testing (and never been part of any stable release), I think it is solved. On the other hand, python-sqlite does not. I Cc this mail to Joel, as python-sqlite does *not* depend on any sqlite package (maybe here is my overlook with python-pysqlite2 ?). So I think the best would be a rebuild of python-sqlite with the current libsqlite3-dev package. No upload is necessary, as Debian supports package rebuilding when the underlying libs change; like in this case. Regards, Laszlo/GCS
signature.asc
Description: This is a digitally signed message part
