Description of problem: In Fedora 37, sqlitebrowser currently is built with (static) version 3.34.1 of sqlite3 but the sqlite3 package is currently version 3.40.0. There a number of small but annoying differences between the two versions. Version-Release number of selected component (if applicable): 3.13.0-0.4.gita302128.fc37 How reproducible: Always Steps to Reproduce: 1. In sqlitebrowser execute the SQL "SELECT format('%s', 'Hi');" 2. 3. Actual results: Execution finished with errors. Result: no such function: format Expected results: Hi Additional info: The version of sqlite3 actually used in sqlitebrowser can be found by executing "SELECT sqlite_version()" sqlitebrowser appears to be statically linked. Is it possible to dynamically link to the latest sqlite3 libraries?
sqlitebrowser is definitely not built statically linked to sqlite, but it is built dynamically linked to libsqlcipher, you should be able to verify this via $ ldd /usr/bin/sqlitebrowser | grep sqlcipher libsqlcipher-3.39.2.so.0 => /lib64/libsqlcipher-3.39.2.so.0 (0x00007f2aabf41000) sqlcipher is a fork of libsqlite which adds 256 bit AES encryption. Perhaps what you are seeing is that sqlcipher in F37 is based on an older sqlite than what F37 ships as libsqlite3.
Ah. That would be it. I have sqlcipher 4.4.3 and looking at the sqlcipher git, the last merge prior to that was sqlite 3.34.1. Even at sqlcipher head the most recent merge is sqlite 3.94.4. I can see encryption might be important for some, but the version skew seems undesirable. Is there a way to accomodate both? For now I have built my own sqlitebrowser.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.