OBS Maintenance

The Osmocom binary packages are built with OBS (Open Build Service) hosted on In order to do that, the jenkins jobs Osmocom_OBS_latest / _nightly (config) checkout the source repositories and build debian source packages, then upload these to OBS.

Install osc

Get the command-line client for managing OBS. When using for the first time, it will ask for the credentials.

$ sudo apt install osc
$ osc ls

Using in meta configs

Each OBS project with packages (e.g. osmocom:nightly, your home: project) depends on other projects for the Linux distributions that the packages should be built for (Debian:12 etc.).

This is defined in the "meta" configuration, e.g. here:

In the past we had a direct dependency on openSUSE's OBS instance for these. This had the disadvantage that we couldn't build packages whenever there was an outage at openSUSE's OBS instance.

<path project="" repository="standard"/>

Nowadays we have a jenkins job that syncs the projects from openSUSE's OBS to our OBS once a day. These synchronized projects are under and can be used as follows:

<path project="" repository="standard"/>

Adding or removing distributions is described in this article.

Upgrading specific packages


See the article upgrading eclipse-titan in the Osmocom OBS.

nftables / libnftnl

Eventually the nftables version >= 1.0.2 that osmo-upf requires should make it into the distributions we support, at which point we can remove the nftables and libnftnl packages. Until then we build these packages in OBS, this section describes how to upgrad them.


As of writing, the nftables and libnftnl packages from the Osmocom OBS are linked to When the package gets upgraded there, the build will fail in the Osmocom OBS with:

[   29s] error: Bad source: /home/abuild/rpmbuild/SOURCES/libnftnl-1.2.4.tar.bz2: No such file or directory

That is because the source tarballs get upgraded, but the spec file has differences and so it does not get upgraded automatically.

Diff the upstream spec file against the one in the Osmocom OBS and apply the changes, then it should work again.

$ $EDITOR /tmp/upstream.spec  # put the upstream spec file here
$ mkdir /tmp/obs
$ cd /tmp/obs
$ osc co osmocom:nightly libnftnl
$ cd osmocom:nightly/libnftnl
$ diff libnftnl.spec /tmp/upstream.spec
$ $EDITOR libnftnl.spec  # apply changes
$ diff libnftnl.spec /tmp/upstream.spec  # verify
$ osc commit
$ rm -rf /tmp/obs

Wait until the package has built, then copy it to the other feeds:

$ osc copypac osmocom:nightly libnftnl osmocom:latest
$ osc copypac osmocom:nightly libnftnl osmocom:master


$ mkdir /tmp/obs
$ cd /tmp/obs
$ osc co osmocom:nightly libnftnl-deb
$ cd osmocom:nightly/libnftnl-deb
$ osc del *

Download the debian source package files into the directory and add them.

$ osc add *
$ osc commit -m "upgrade to 1.25" 
$ rm -rf /tmp/obs

Wait until the package has built, then copy it to the other feeds (see rpm).

Workflow for testing OBS configurations

OBS has a project configuration, which may need to be adjusted to state preferred dependencies for example. Before we apply project configurations to the official Osmocom OBS projects, we can test them in our own OBS project. Copy the relevant package first (adjust the username accordingly in all following examples):

$ osc copypac osmocom:nightly osmo-gsm-manuals home:osmith42
Visit the site in your browser: Set up build targets:

The package should get added to the queue already.

Open your project config next to the osmocom:nightly one:

First copy everything from the Osmocom project over to your own project. Then make changes to your config, until the builds are working as expected (dependency problems are resolved etc.). Whenever you change the config, OBS will immediately re-evaluate the build dependencies, no need to upload the source packages again.

When everything works as expected, copy the config changes you have made to the Osmocom project (nightly and latest).

Note that changing osmocom's project config did not seem to have any effect. It seems that we really must change both osmocom:nightly and osmocom:latest instead.

Workflow for modifying packages

(Optional) modify the debian dir

  • clone the source git repository
  • make changes to the debian dir
  • commit your changes
  • push to a "user/..." branch

Build source packages and upload to your own OBS project

  • clone osmo-ci.git
  • open
  • if you intend to make changes to the script, do them and commit the changes
  • change PROJ to home:USERNAME
  • if you made changes to the debian dir, insert your branch name after the related checkout line (e.g. checkout osmo-gsm-manuals osmith/some-random-change)
  • run
  • check in your browser if all packages have been built by OBS as expected (iterate until you get everything right)

When everything works fine, contribute your patches with Gerrit as usually.


A script must run before building the source package (to download dependencies etc.)

If we have control over the git repository, we can add a contrib/ script to it (example). It will be executed by the OBS scripts when building source packages.

Otherwise add a prepare_project_ function to scripts/obs/lib/ in osmo-ci.git. See the existing functions there for reference.

Source tarball not found

If a build suddenly fails with an error like this:

[   49s] error: File /home/abuild/rpmbuild/SOURCES/zeromq-4.3.4.tar.gz: No such file or directory

Then it is probably linked to an upstream package from openSUSE OBS and needs to be adjusted. We have it set up like this to automatically get new versions if they are packaged upstream. However the downside is that oftentimes we need to adjust the spec file, which means that it can't automatically be updated. Therefore the new source tarball gets added (in the example zeromq-4.3.5.tar.gz), but the spec file still mentions the old version.

How to fix it:
  • Follow the links on our OBS to the upstream project (example)
  • Look at the diff of the upgrade (example)
  • Apply the changes to our spec files (usually in osmocom:latest, osmocom:nightly, osmocom:master)

Package is not resolvable

have choice for jadetex needed by docbook-utils: jadetex texlive-formats-extra

You'll need to adjust the OBS project configuration (mind the testing workflow above):

Prefer: texlive-htmlxml

Reproduce the nightly builds locally

$ osc co
$ osc build

E-Mail Notifications of build failures

Build failure notifications are sent to the gerrit-log mailing list

See also

Updated by osmith 4 days ago · 27 revisions

Add picture from clipboard (Maximum size: 48.8 MB)