Changes

lint/checkpatch: ignore SSCANF_TO_KSTRTO

This kernel-specific warning doesn't make sense when linting our code so
disable it.

Change-Id: If096c600331d7ad5786395c5c41a6742da44a3e8

OBS: add Ubuntu 26.04

Change-Id: Id22f4902b73ad9b4131b837a8036df68cf665f8f

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

jobs: add build/manuals JOB_TYPEs for osmo-s1gw

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

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/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

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

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

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

octsim_osmo-ccid-firmware: add myself to the recipients

Change-Id: I2b96ad0d34e4344ccb0351737df31b08cb65e116