Your message dated Sun, 15 Oct 2006 18:46:59 +0200
with message-id <[EMAIL PROTECTED]>
and subject line sqlite3 vs pysqlite version malfunctions
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: sqlite3
Version: 3.3.5-0.1
Severity: normal
sqlite >= 3.3.3 exposes a bug in some pysqlite versions.
Specifically, the bug is present in:
The 2.0.x series, << 2.0.7 (package: python-pysqlite2)
The 1.1.x series, << 1.1.7 (package: python-pysqlite)
The 2.1.x series, << 2.1.3 (not in Debian)
Relevant release announcements are:
http://lists.initd.org/pipermail/pysqlite/2006-February/000378.html
http://lists.initd.org/pipermail/pysqlite/2006-February/000372.html
http://lists.initd.org/pipermail/pysqlite/2006-February/000373.html
The bug in pysqlite causes almost all operations to fail with the error
message "You can only execute one statement at a time".
Would it be appropriate for sqlite3 >= 3.3.3 to conflict with the broken
pysqlite versions?
I think that would be:
Conflicts: python-pysqlite (<< 1.1.7), python-pysqlite2 (<< 2.0.7),
python2.3-pysqlite (<< 1.1.7), python2.4-pysqlite2 (<< 2.0.7),
python2.3-pysqlite (<< 1.1.7), python2.4-pysqlite2 (<< 2.0.7)
Ideally, it would also conflict with python*-pysqlite2
versions '>= 2.1 AND << 2.1.3', but I don't think dpkg can represent
that sort of relationship, can it?
Thanks,
Max.
--- End Message ---
--- Begin Message ---
As this is solved with new package versions, reporter agrees that no
further action needed.
Thanks Max anyway for your time!
--- End Message ---
