Commit Graph

13 Commits

Author SHA1 Message Date
Pau Espin 7eefae4b01 Bump version: 1.10.0.125-92caa-dirty → 1.11.0
Change-Id: Ifc4bfe8b4154fa892a4d15d54cee34b501038c20
2023-09-12 16:46:12 +02:00
Pau Espin 964ce6f46c Bump version: 1.9.0.58-1289-dirty → 1.10.0
Change-Id: Ifff00a3107447da911629948e9f3061c93b6ac86
2023-02-07 17:28:17 +01:00
Pau Espin 5b06a8d6a5 Bump version: 1.8.0.43-2eaaf-dirty → 1.9.0
Change-Id: Iacb839715290b27f1f3d302e13f219f5f0e1d161
2022-06-29 11:32:12 +02:00
Harald Welte 2eaaf6f305 fix RPM build failures due to README -> README.md rename
This fixes a bug I introduced in I98e09e8900c359382e2a90b187f0c6f22a1cf81d

Change-Id: I9d7bc0aea404499315e212a2ebb92d54df85d812
2022-06-21 09:50:53 +02:00
Harald Welte d43c22ef65 switch from libdbi to lbsqlite3
The choice of libdbi was one of the biggest early mistakes in (back
then) OpenBSC development.  A database abstraction library that
prevents you from using proper prepared statements.  Let's finally
abandon it and use sqlite3 directly, just like we do in osmo-hlr.

I decided to remove the database migration code as it would be relatively
cumbersome to port all of it to direct sqlite3 with prepared statements,
and it is prone to introduction of all kinds of errors.  Since we don't
have a body of older database files and comprehensive migration tests,
it is safer to not offer migration code of uncertain quality.  The last
schema revision (5) was introduced 5 years ago in 2017 (osmo-msc
v1.1.0), so it is considered an exceptionally rare case.  People can
install osmo-msc 1.1.0 through 1.8.0 to upgrade to v5 before using
this new 'direct sqlite3' version of osmo-msc.

Change-Id: Ia334904289f92d014e7bd16b02b3b5817c12c790
Related: OS#5559, OS#5563, OS#5564
2022-05-17 14:04:44 +02:00
Harald Welte 467fc5728d switch sqlite3 to single-threaded mode
Looking at 'perf top' of osmo-msc under load shows that there's a
significant amount of time spent in terms of locking (mutex,...)
which is useless as osmo-msc is a single-threaded application.

Unfortunately libdbi doesn't provide a mechanism to perform
sqlite3_config(), so we have to do it directly here, introducing an
explicit build-time dependency (and linkage) to libsqlite3.

Related: OS#5559
Change-Id: I5bbea90d28b6d73b64b9e5124ff59304b90a8a75
2022-05-15 13:04:56 +02:00
Pau Espin b7f97ea8a0 Bump version: 1.7.0.43-aefbf-dirty → 1.8.0
Change-Id: I37aa63e1c4ed021c5cc8b186f073cf01ab9a9cb6
2021-11-16 17:44:54 +01:00
Oliver Smith 4ac59538e9 contrib/osmo-msc.spec.in: require libosmo-ranap >= 0.7.0
Sync with configure.ac, debian/control. Nowadays osmo-release.sh
complains about this.

Related: I8dbbd63fdbd35f5f90f20dcd7e710078f2d9e12a
Change-Id: Ib3b9d6af8f9d4e807ff4106f95f0a5b13834a126
2021-09-16 14:34:18 +02:00
Oliver Smith 5a44e5f46e contrib/osmo-msc.spec.in: depend on dbd-sqlite3
Add the missing runtime dependency to the sqlite3 driver of libdbd.
The library does not provide a pkgconfig file, so using "pkgconfig(...)"
as done in the BuildRequires is not possible. Write both the OpenSUSE
and CentOS name with an if..else.

Fixes:
  <0009> db.c:648 Failed to create database connection to sqlite3 db 'sms.db';
                  Is the sqlite3 database driver for libdbi installed on this system?

Change-Id: Ia972944c300aecbb6ec460b2362aabff459baefd
2021-03-09 14:48:59 +01:00
Pau Espin 59764b6f3e Bump version: 1.6.1.98-cad22-dirty → 1.7.0
Change-Id: I1bf25c0c01efd6f93df8ac2b26868dd1579b3531
2021-02-23 20:22:34 +01:00
Harald Welte a4a45252df osmo-msc.spec.in: Use %config(noreplace) to retain current config file
Change-Id: I00c3152b774a826230a112eae93b0e7c4d4f4c7a
2020-06-23 20:07:56 +00:00
Harald Welte 5c38c817f2 contrib/osmo-msc.spec.in: Enable SMPP in RPM builds
The SPEC file already included a build dependency to libsmpp34, but
then the compilation of osmo-msc didn't actually pass --enable-smpp
along, resulting in binaries without SMPP support - unlike the Debian
binaries, which do contain that part.

Change-Id: I223be7a735e97b32f7c0ff246cf826f109b0f686
2020-06-13 14:40:32 +00:00
Oliver Smith 0314593aa7 contrib: integrate RPM spec
Remove OpenSUSE bug report link, set version to @VERSION@, make it build
with CentOS 8 etc.

Related: OS#4550
Change-Id: If5499e11d872e629a018fc77d5adf5d0cb863d48
2020-05-20 08:50:18 +00:00