sqlite version mismatch causes problems in Evolution backend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
beagle (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Gutsy |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: beagle
I'm the upstream maintainer of Beagle, and we've found a nasty bug related to Ubuntu's compiling of Beagle against sqlite 3 when previous versions were built against sqlite 2.
The problem essentially is that the Mono sqlite bindings don't gracefully handle using a sqlite 2 database with sqlite 3. While opening of the database connection succeeds (something that doesn't work when a v3 db is opened with v2, and a case we check for), an error is encountered when trying to actually run a SQL statement on the database. Unfortunately this will happen for every Evolution IMAP email that is attempted to be indexed by Beagle.
Unfortunately our two downstream Ubuntu maintainers (Kevin Kubasik and Nirbheek) are without internet connections at present. If someone else can apply the patch I'm attaching to the Gutsy package, that would be greatly appreciated. It has already gone upstream to both our stable 0.2.x branch and the trunk (r4053 and r4054 in GNOME SVN, respectively).
I have a bzr branch with this fix (and a few others) available. Associating with bug report.