> ---8<--- > svn: E200029: Couldn't perform atomic initialization > svn: E200030: SQLite compiled for 3.8.0.1, but running with 3.7.17 > --->8---
Sigh. This kind of problem is usually solved by the shlibs system, but that doesn't fully work here. The problem is that the SQLite "ABI" (usable SQL features, basically) doesn't really correspond to C symbols. Subversion detects the version at build time in order to decide what features to use, so it makes sense to have the runtime check to make sure SQLite is new enough, but it is not obvious how to translate that into the Debian package metadata, except by crude heuristics. Also, the runtime check is very simple, thus it is stricter than it needs to be - probably the sqlite 3.7.17 ABI would have been fine. I've already partially "fixed" the check, but it appears I need to do more. I have an idea for a better (though hacky) approach. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
