Cellular Network Infrastructure » Core Network (CN) » OsmoMSC

Can you try using the binary package feed we provide? Just to exclude any build environments related topics? We di have nightly and latest feed for raspbian and debian on raspi. The debian one should work on ubuntu

I am using the binary packages as follows in the docker

RUN wget https://downloads.osmocom.org/packages/osmocom:/latest/xUbuntu_20.04/Release.key && \
    mv Release.key /etc/apt/trusted.gpg.d/osmocom-latest.asc && \
    echo "deb https://downloads.osmocom.org/packages/osmocom:/latest/xUbuntu_20.04/ ./" > /etc/apt/sources.list.d/osmocom-latest.list && \
    apt-get update && apt-get -y install osmo-msc

Also, I had to install libdbd-sqlite3 separately in order for osmo-msc to work (without sgs section). Or else it used to complain as follows

<0009> db.c:619 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

At least as far as I can tell, in current master (corresponds to the nightly feed), osmo-msc has no optional dependencies or --enable compile flags regarding SGs. SGs is always there, and it cannot be disabled at build time. I also don't recall this ever having been different.

Quite mysterious.

Ah, you are installing the osmo-msc package from ubuntu itself, not from the osmocom package feeds:

#6 13.58 Get:14 http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 osmo-msc arm64 1.2.0-3 [113 kB]

And ubuntu ships an ancient version (1.2.0 from 2018) while our latest tagged version is 1.10.0. The SGs was first introduced in 1.4.0

So whatever you're doing, your APT configuration seems to be set up in a way that it doesn't know of the osmocom repositorires, or tha the priority of an ubuntu package is higher than an osmocom package, even though it has a much lower pacakge version.

laforge wrote in #note-4:

Clearly the libdbd-sqlite3 package should be a mandatory dependency for the osmo-msc package.

Not anymore for the recent packages (both nightly and latest), since osmo-msc is now using libsqlite3 directly.

Thanks a lot for taking a look at this. I didnt realize I was installing the osmo-msc package from ubuntu itself, not from the osmocom package.

We don't do ARM builds for Ubuntu, as in our experience that's a very unusual configuration, and we cannot support every distribution on every architecture. Also, in general, I think Ubuntu is departing more and more from what we know of as Linux distribution over the last 25+ years. It's insistence on moving away from dpkg towards its proprietary SNAP environment makes it a platform that is in my opinion becoming rather non-free.

Ah I see. Then, I will use Debian as base image in my repository then.

Is it okay if I keep this issue open until Monday so that the user can test on his RPi setup and see if he still faces issue or not?

Thank you laforge . Issue is resolved by using latest osmo-msc package. This issue can be closed.