#1143 (Mar 27, 2026, 9:04:58 AM)

OBS: sync_obs_projects: fix for OSC 1.12.1

Since the Docker image used by sync_obs_projects was changed from Debian
12 to 13, several "osc" commands have in their output:

  fatal: not a git repository (or any of the parent directories): .git

Work around this by switching to the temp directory and initializing a
git repository there, with an "origin" remote that osc also expects to
exist.

Fixes: 6ac535b8 ("OBS: set default distro to debian 13")
Change-Id: I1236a065e2998fb46343df3968f7bb4dabeea55a

jobs/ttcn3: add -ogs-latest jobs

Be consistent with the Osmocom jobs where we have -latest too.

Add no mail notifications to open5gs maintainers, because if tests start
failing for latest then it usually means a regression in our testsuite
code.

Change-Id: I28c3b7130661c177271d7341f759a05c94d9607f

jobs/ttcn3: add ttcn3-hss-test-pyhss

Depends: I224eb4aa5fec3dc97f6fa956a4a86f206c8b12b7
Related: OS#6862
Change-Id: I517d36d890690e606050158221d2df9028745dae

jobs/ttcn3: adjust to testenv config rename

Replace "-c osmo_{hlr,ggsn}…" with "-c osmo".

Depends: osmo-ttcn3-hacks I7a64c946ece8ad5bfbf4f7d613634138af6db566
Change-Id: I3766d76a5a6fa8a8de00137fe33e0e747337c66e

jobs: libosmo-sigtran: add support for TCAP loadsharing

TCAP loadsharing requires an additional library libosmo-asn1-tcap.
./contrib/jenkins.sh is using the env TCAP={0,1} to select this feature.

Unclear if we should also put it into our default build.

Change-Id: I47c193d8f5ce695fdc6c368eee94d21c5a4b2c6e

lint: run clang-format only on specific projects

For most C projects, running checkpatch works best with the coding style
we use. Run clang-format only in specific projects that seem to be fully
formatted with that tool.

Related: https://gerrit.osmocom.org/c/osmo-mgw/+/41529
Related: https://gerrit.osmocom.org/c/osmo-asf4-dfu/+/39470
Related: https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/39471
Change-Id: I2c07b30f9254b54027b721b77ab6f35249b5e2de

scripts: Add libosmo-asn1-tcap to OSMO_RELEASE_REPOS

Change-Id: I76703ed5c648eb50574166f8459fd0bde1720902

ansible: jenkins: mount tracefs via fstab

Allow using bpftrace inside the jenkins lxc containers by making
/sys/kernel/tracing available through /etc/fstab.

Related: OS#6794
Change-Id: I568e3635fcc33040036fd19e9226b413db0d3ef3

jobs/ttcn3-testsuites: set RUN_BPFTRACE=1

Allow better analysis of instabilities with the ttcn3-bts-test jobs in
jenkins by running bpftrace scripts along with osmo-bts.

Only the ttcn3-bts-test scripts make use of the RUN_BPFTRACE environment
variable, so this does not affect how any other testsuite runs.

See the related docker-playground commit for details.

Related: OS#6794
Related: docker-playground I5c22cdbb08fe797be936ca174f65ade626fa4895
Change-Id: Iaa960772fb0b09722594747006890e5e43752d43

contrib/known_hosts: update gerrit ssh key

Related: OS#6920
Change-Id: I66e5d96dcb34d33a21f5a70899fba9a75e6127ed

scripts/manuals: use debian-trixie-build

Fix that the Osmocom-release-manuals job was still using
debian-bookworm-build instead of debian-trixie-build to build the
manuals. We use the latter for building manuals in master-builds and
gerrit-verifications.

Without this patch building pyosmocom manuals failed with the following,
as python3-typing-extensions in debian bookworm is at version 4.4.0 but
typing_extensions >= 4.6.0 is needed for TypeAliasType. Trixie has
version 4.13.2.

AttributeError: module 'typing_extensions' has no attribute 'TypeAliasType'. Did you mean: 'TypeAlias'?

Fixes: OS#6916
Change-Id: I6ac302c8ea5836c5096f0d8ab36260cc6f7c11d9

jobs/ttcn3-testsuites: disable bpftrace

The bpftrace process doesn't stop properly with some scripts. Disable it
for now, we can still enable it in copies of the job.

Related: OS#6925
Change-Id: I78c18c2e18d66408ac7de7cd24fafdf3f7e5202d

ansible: allow jenkins users to set rtprio 30

Create an /etc/security/limits.d file to allow the jenkins user to set
rtprio 30. This is required for running the ttcn3 bts testsuite through
testenv, as (unlike the previous approach with docker containers)
osmo-bts-trx runs without root rights there.

Change-Id: Id79851b3e3a47d19773aa9bba134b9bf99dbecbb

jobs/dahdi: fix git clones not getting updated

The refspec line has caused the git clones of the linux kernel to not
get updated.

Fixes: OS#6932
Change-Id: Id3b35ac10cf4fcb244c572a319433379e2e59c22

jobs/dahdi: add linux-6.12

Closes: OS#6931
Change-Id: Ia5bd796e1cdf6f0f22fe0cba1546c4487d847c30

jobs/gerrit: debian10 for osmo-gbproxy + deps

Related: SYS#7859
Change-Id: I7ad3412d945de8c29b6ab62fcadfd2f231c19581

repo-install-test: test osmo-pfcp-tool in latest

osmo-pfcp-tool is available in latest for quite some time now, so adjust
the check.

Related: osmo-upf Icf4bb566d9b627ead370174e92629a9fccde755e
Change-Id: Icca5a31270bca03596be8ed0104bfb7143fb1ede

repo-install-test: debian 10: osmo-gbproxy only

The debian 10 repository has been officially disabled:
https://osmocom.org/news/308

However we just re-enabled a subset of the packages, osmo-gbproxy +
dependencies, because currently they are relevant for a customer. Adjust
the repo-install-test to deal with this subset of packages for debian 10
to fix that it is currently failing.

I have verified that repo-install-test works with this change for debian
10, 11 and 12. It currently doesn't run for debian 13 yet (OS#6934).

Related: SYS#7859
Change-Id: Id8d8cda8e399719f06aeb1843eb8f5ab12a90e8f

Osmocom_OBS_sync: fix failing on new scmsync tag

The openSUSE OBS instance has added an scmsync tag to their debian 13
meta config:

  <scmsync>https://src.opensuse.org/obs/debian#13</scmsync>

This feature is not supported by the stable OBS version yet (they run
current master), and so the sync fails with:

  project validation error: 6:0: ERROR: Element project has extra content: scmsync

Remove the tag to fix this.

Related: https://build.opensuse.org/projects/Debian:13/meta
Change-Id: Ia2d2ce3a2eeda9a0ed7ce7c7de54293081b44f4e

scripts/kernel/linux-shallow-clone: new script

Add a script that maintains a linux repository in one place on jenkins
nodes, so we need less git clones from git.kernel.org and less disk
space. All jobs that need a kernel tree can now clone the relevant
branch directly from the jenkins node.

Follow up patches will add a jenkins job that runs the script daily and
adjust the existing jobs to make use of this instead of doing their own
clones.

Currently this script produces a 396M bare git repository.

Related: OS#6938
Change-Id: Id3aadb46813047ecac3b80868192809b272dba0e

jobs/linux-shallow-clone: new jenkins job

Related: OS#6938
Change-Id: Ia58cdc82a655d4cc772a84adb675e98961bf86c5

jobs/master-builds-dahdi: use linux-shallow-clone

Related: OS#6938
Change-Id: Iea0af6259bd481c946ff72d6552b65668fd809ca

jobs/gerrit-verifications-dahdi: use linux-shallow-clone

Related: OS#6938
Change-Id: Ie8d9be886cc1d089e015f03bcedf0307f4f312e4

jobs/build-kernels-testenv: use linux-shallow-clone

Related: OS#6938
Change-Id: I8cb2acfaf585b9f92347a4562525a66ed03b0236

octsim_osmo-ccid-firmware: add myself to the recipients

Change-Id: I2b96ad0d34e4344ccb0351737df31b08cb65e116

lint/checkpatch: fix false FUNCTION_ARGUMENTS

Fix that the linter complains about:
  WARNING:FUNCTION_ARGUMENTS: function definition argument 'void' should also have an identifier name

For functions with attributes at the end, e.g.:
  void Fallback_Handler(void) __attribute__((weak, alias("Dummy_Handler")));

Related: https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42224/comment/7c5b3be0_6ff61090/
Change-Id: I139bdabb38bd0c9ceda99921ebdc0196850c2a53

lint/checkpatch: support multiple configs

Run checkpatch with any .checkpatch*.conf found in the project dir. This
is in preparation for having two .checkpatch.conf files in osmo-trx, in
order to use different linting rules for C++ code:
* .checkpatch.c.conf
* .checkpatch.c++.conf

Related: osmo-trx I0df5b6f2f0bf1469a80a1f5859809c30f523f683
Change-Id: Ia2e75d9783382cefc3900a4ab51a5a919a2cbbbc

repo-install-test: don't use deprecated apt-key

apt-key has been removed in debian 13, use "[signed-by=…]" instead.

Change-Id: I7b8b9336b16cceb7ece317c59de2f55ed404392e

repo-install-test: fix test_conflict for debian 13

Two changes are necessary to make this test work with debian 13:

* Installing libosmocore from osmocom-latest, then switching to
  osmocom-nightly and attempting to install another package is not
  enough anymore to trigger a conflict. apt is now able to resolve this
  by uninstalling the osmocom-latest package and upgrading libosmocore
  to the nightly version. Force the conflict by explicitly marking
  osmocom-latest (osmocom-$FEED) as installed and for hold.

* The apt conflict message has been reworked, so the string to look for
  needs to be adjusted.

Change-Id: Ibdcd583e48b97ced11ad4939974dccea3e139480

repo-install-test: ignore sdcc-dbgsym

Fix for this error with debian 13:

  The following packages have unmet dependencies:
   sdcc-dbgsym : Depends: sdcc (= 4.2.0~osmocom3.113.9edd) but 4.5.0+dfsg-1 is to be installed
  E: Unable to correct problems, you have held broken packages.
  E: The following information from --solver 3.0 may provide additional context:
     Unable to satisfy dependencies. Reached two conflicting decisions:
     1. sdcc:amd64=4.2.0~osmocom3.113.9edd is not selected for install
     2. sdcc:amd64=4.2.0~osmocom3.113.9edd is selected for install because:
        1. sdcc-dbgsym:amd64=4.2.0~osmocom3.113.9edd is selected for install
        2. sdcc-dbgsym:amd64 Depends sdcc (= 4.2.0~osmocom3.113.9edd)

Change-Id: Ibb12118853f354d177cb94df63b60dd3bd9dfcb7

repo-install-test: ignore charon-systemd

This package from strongswan-epdg causes the SSH connection to QEMU to
break when installed in debian 13. Don't install it. Use the wildcard,
because there is also a debug symbols package that pulls in
charon-systemd.

Change-Id: Ic641d5361c51df147a8cef5d49eb1e0f07b72e87

repo-install-test: ignore pyhss

PyHSS listens on the same port as OsmoHLR, which causes the test to fail
with debian 13 because OsmoHLR can't start up properly. PyHSS wasn't
built for earlier debian versions in the Osmocom binary repositories.

Change-Id: I796e85a212dff94fbf9b8ef563eba47418c221cc

repo-install-test: run for debian 13 too

This passes for latest, and should pass for nightly once this patch is
merged: https://gerrit.osmocom.org/c/osmo-sgsn/+/42277

Change-Id: I1db9de8c740d5167e4813ece36f422b27aed5111

jobs/gerrit-lint: use debian 13

Use debian 13, so we have a newer clang-format version (14 -> 19).

Change-Id: I747dce009bb2e91f16a15e79dbe274c162f64813

lint/lint_diff: print clang-format version

Change-Id: I076a518dccdb241a57628c385a60bffe30298a10

ansible: osmocom-obs-worker: remove lxc<5

I have applied a patch in our OBS server, which adjusts the version
check so we can build packages with newer LXC versions and sent it
upstream: https://github.com/openSUSE/obs-build/pull/1127

Remove the lxc version constraint (which finally allowed upgrading to a
newer opensuse version).

Related: OS#6975
Change-Id: I1e690bf91c4bebd1d46b51ec490daa339ea1107f

ansible: osmocom-obs-worker: add mount-securityfs.service

Fix errors in lxc-start related to not having securityfs available:

[   14s] booting lxc...
[   14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1132 If you really want to start this container, set
[   14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1133 lxc.apparmor.allow_incomplete = 1
[   14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1134 in your container configuration file
[   14s] lxc-start: obsbuild:root_6: start.c: lxc_init: 879 Failed to initialize LSM
[   14s] lxc-start: obsbuild:root_6: start.c: __lxc_start: 2008 Failed to initialize container "obsbuild:root_6"
[   14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 306 The container failed to start
[   14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options
[   14s] '/var/cache/obs/worker/root_6/.build/_exitcode' not found or symlink

Usually systemd would mount the securityfs automatically as I understand
it, but it doesn't work anymore without this service in our use case
where osmocom-obs-worker runs inside an LXC itself. This is probably
related to upgrading the opensuse version for the osmocom-obs-worker
containers.

Change-Id: I0c708815440c67340531548361deb326c864aefe

ansible/hosts: update lx2-1-obs-aarch64-1 ip

This machine is not available under the listed IPv6 anymore, but can be
reached through the VPN. Adjust the IP.

Change-Id: I77f72d7ad72d9b3ac745756cc5a082bd39dabdc5

jobs: add build/manuals JOB_TYPEs for osmo-s1gw

Change-Id: Id62d806a648c8f3480cb4f162adf65f77c552848
Depends: osmo-s1gw.git I54f0774575534519a2c40e0588f136c8a5e706f8
Related: OS#6671

manuals: ignore old osmo-s1gw tags

Logic for building the osmo-s1gw-usermanual.pdf has just been added to
master. The Osmocom-release-manuals job tries to build old manuals as
well because now the osmo-s1gw directory exists at
https://ftp.osmocom.org/docs. Ignore old tags, as we can't build
usermanuals for those.

Change-Id: I94f19db2861f16c45894573f52f30bfbf5a7725e

manuals: osmo-s1gw: adjust build_publish_manuals

Use the proper command to build osmo-s1gw manuals, so it doesn't fail
with:
  + su build -c autoreconf -fi
  autoreconf: error: 'configure.ac' is required

Change-Id: I096fd34fc5819becbc3a08a2dc4065d4913bbc1b

OBS: add Ubuntu 26.04

Change-Id: Id22f4902b73ad9b4131b837a8036df68cf665f8f

OBS: pyhss_download_deps: fix dependency loop

Fix that the Osmocom_OBS_nightly job is failing for the pyhss package
with a dependency loop in hatchling:

  LookupError: https://files.pythonhosted.org/…/hatchling-1.29.0.tar.gz (from https://pypi.org/simple/hatchling/) (requires-python:>=3.10) is already being built: hatchling>=1.21.0 from https://files.pythonhosted.org/…/hatchling-1.29.0.tar.gz

This happens as it recursively collects source packages and their
(build) dependencies:

  pymongo
  -> dnspython
  -> hatchling
  -> pluggy
  -> setuptools-scm
  -> vcs-versioning
  -> hatchling

When only ignoring the hatchling source package, we get a similar
dependency loop with pluggy, so ignore both source packages. Hatchling
gets added later as binary package and pluggy is only a build-time
dependency for hatchling. The resulting PyHSS package builds fine with
this change.

Change-Id: I0484627fd105627fabe9435379e704db54e72ae3

OBS: pyhss_download_deps: add python 3.14

Download binary package dependencies for python 3.14 too, so we can
build the package for Ubuntu 26.04.

Related: https://gitea.osmocom.org/osmocom/pyhss/commit/2125f52c5eb1b3e66b1ebe2febadb7c886536681
Change-Id: Ic23d52c081f68fb8d6f7d9e370883236ca9bf35f