Your message dated Sun, 05 Jul 2009 12:57:24 +0200
with message-id <1246791444.4552.56.ca...@julia.gcs.org.hu>
and subject line Re: Bug#522103: sqlite ABI breakage: any progress?
has caused the Debian Bug report #522103,
regarding libsqlite3-0: ABI breakage: xCheckReservedLock method in
sqlite3_io_methods changed prototype
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
522103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsqlite3-0
Version: 3.6.11-4
Severity: serious
The sqlite3_io_methods struct, which just contains pointers to different
functions, changed in an incompatible way, by making one of these
methods (xCheckReservedLock) accept two parameters instead of one.
We had a long chat about this on #debian-release today, because
evolution-data-server makes use of the VFS layer in sqlite3, and broke
when compiled against 3.5 and run against 3.6 (see #519428).
It is unclear to us what is SQLite’s compromises regarding this API,
since it is true it’s a very low-level functionality, and possibly the
SQLite authors are expecting for code using it to be compiled together
with SQLite itself. But, alas, it gets exported via sqlite.h, so...
We are going to rebuild evolution-data-server in unstable as to give a
temporary fix to the issue. We don’t know if other applications are
affected, and we should assess what permanent solution to give to this
problem.
We’ll get back to you on this; I’ve filed this bug for tracking purposes.
--
- Are you sure we're good?
- Always.
-- Rory and Lorelai
--- End Message ---
--- Begin Message ---
Hi Francesco,
On Sun, 2009-07-05 at 12:19 +0200, Francesco Poli wrote:
> Any progress on this bug?
I'm closing it now. Read on if interested.
> I hope it may be fixed soon.
It is fixed ages ago. Evolution used one of SQLite3 internal function
which is changed. New version of Evolution uploaded fixed this. No other
program is affected nor in binary, nor in source form. I mean no other
bugreport / crash related to this internal function change is known
since four months.
About sources: I have compiled a lot of SQLite3 reverse depends without
any problems. These include python and its modules, evolution, php5,
balsa, bacula, xulrunner-1.9, bogofilter, xmms2-core, amarok, liferea.
As Florian Weimer seconded, it was the fault of Evolution to use an
SQLite3 internal function. It was corrected and no other steps needed
from the SQLite3 side.
Regards,
Laszlo/GCS
--- End Message ---
