-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Laszlo Boszormenyi wrote: > 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.
Whoa! The misunderstandings are piling up here! (1) Regarding python-sqlite No action is necessary at all. It was my mistake to mention the package at all. Instead, the package I should have mentioned is 'python-pysqlite1.1'. (2) Regarding the presence of dependencies None of the 'python-*sqlite*' packages have sqlite dependencies, as they are dummy packages, whose only purpose is to depend on the 'python2.3-*sqlite*' versioned variants. (3) Regarding the need for binNMUs There is NO need for any binNMUs here. The current packages work fine. The only reason I submitted this bug was to suggest that it _might_ be appropriate to document the broken versions using a versioned conflicts statement. However, checking the PTS, I see that neither the python-pysqlite1.1, not the python-pysqlite2, packages were present in sarge, and the older buggy versions have been replaced with newer fixed versions in sid and etch. In conclusion, then: There was an incompatibility between certain upstream versions of sqlite and pysqlite, but the affected versions are no longer in the Debian archive. If you feel it appropriate, you may wish to document the incompatibility in a conflicts relationship. Otherwise, I am content for this bug to be closed with no further action taken. Max. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) iD8DBQFEVkfAfFNSmcDyxYARAmPGAJ9AcD6NPHAshpTVCA9DsC9enH8MmACdHnlA IgpiHrMgdWgy2tBq4WYRqWI= =e6Ii -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
