Dear Christian, There is a considerable change on sqlcipher where they synchronized the build system with sqlite3.
There is no recommendation from the upstream to choose the soname downstream. The current upstream libsqlcipher soname for the library seems inspired from sqlite3 version. https://sqlite.org/releaselog/3_50_4.html https://github.com/sqlcipher/sqlcipher/blob/master/CHANGELOG.md#4100---august-2025---4100-changes The bump of soname from 1 -> 2 is debian specific. More details are available on the choice of soname : https://github.com/sqlcipher/sqlcipher/issues/488 In the previous sqlcipher version (trixie): pkg-config --print-provides sqlcipher sqlcipher = 3.46.1 pkg-config --print-provides sqlite3 sqlite3 = 3.46.1 dpkg -L libsqlcipher1 /usr/lib/x86_64-linux-gnu/libsqlcipher.so.1.8.0 .. /usr/share/lintian/overrides//usr/lib/x86_64-linux-gnu/libsqlcipher.so.1 In sqlcipher(unstable) pkg-config --print-provides sqlcipher sqlcipher = 3.50.4 sqlite3 is still at 3.46.1 version. pkg-config --print-provides sqlite3 sqlite3 = 3.46.1 Regards, Syed Shahrukh Hussain.
