Package: libsqlcipher0 Version: 3.2.0-1 Severity: important Dear Maintainer,
While debugging an error with pysqlcipher that made the database not write data to disk [0], for which a sample script is available [1], I found that the following patch in the debian package for libsqlcipher is interfering with the behavior of the code that relies on SQLITE_VERSION_NUMBER: 20-change-name-to-sqlcipher.patch The string set in the VERSION file is exported as SQLITE_VERSION_NUMBER in the headers. Since there are several checks (internal to the sqlcipher implementation, and in this case in the code for the c extension for pysqlcipher) that depend on SQLITE_VERSION_NUMBER, I'd suggest to add a different string, SQLCIPHER_VERSION / SQLCIPHER_VERSION_NUMBER and leave the original sqlite version string as in upstream, in order not to break code that depends on the origianl sqlite version which sqlcipher is based upon. In the short term, just skipping this patch will make the package usable for us again, greatly improving the situation. (note that the same problem affects also the version in wheezy-backports). [0] https://leap.se/code/issues/6688 [1] https://leap.se/code/attachments/318/test-sqlcipher2.py -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libsqlcipher0 depends on: ii libc6 2.19-13 ii libssl1.0.0 1.0.1k-1 ii multiarch-support 2.19-13 libsqlcipher0 recommends no packages. libsqlcipher0 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
