Bug #3771
osmo-msc Debian package does not depend on libdbd-sqlite3
100%
Description
Therefore it fails to start up with:
<0009> db.c:621 Failed to create database connection to sqlite3 db 'sms.db'; Is the sqlite3 database driver for libdbi installed on this system? DB: Failed to init database: sms.db
Found this while fixing #3767.
Related issues
History
#2 Updated by pespin 3 months ago
I think it is expected that it's not installed by default, since the point of using libdbd there (anyway will be removed at some point afaik) is that you can use whatever backend you prefer, so you should not force installation of specific libdbd-sqlite3. The error message is detailed enough for users to understand the specific backend is missing.
I think we can close this issue.
#3 Updated by osmith 3 months ago
pespin wrote:
I think it is expected that it's not installed by default, since the point of using libdbd there (anyway will be removed at some point afaik) is that you can use whatever backend you prefer, so you should not force installation of specific libdbd-sqlite3.
I agree with you, that if it was possible to choose the backend, then we should not force installing libbd-sqlite3. However, looking at the code, sqlite3 is hardcoded. Users would need to patch db.c and recompile it to use another backend. So if the only possible way to use the binary package of osmo-msc is with libdbd-sqlite3 (as it is now), then it should be a dependency in my opinion.
#4 Updated by laforge about 2 months ago
- Assignee changed from sysmocom to osmith
I agree with osmith. We require sqlite3, and until we remove the libdbd dependency altogether (no more internal smsc), we should fix the dependencies accordingly.
#5 Updated by osmith about 2 months ago
- Status changed from New to In Progress
- % Done changed from 0 to 90
Patch submitted:
https://gerrit.osmocom.org/#/c/osmo-msc/+/13043/
#6 Updated by osmith about 2 months ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
