Started by timerBRANCHmaster001616140645714064571.00333039538efe3cfcfb65a150604d6ee49f7b3540c44458538efe3cfcfb65a150604d6ee49f7b3540c44458origin/master538efe3cfcfb65a150604d6ee49f7b3540c44458538efe3cfcfb65a150604d6ee49f7b3540c44458origin/master2625c792b8c79ee92af6a34c4c06ec01a985c8902f94c792b8c79ee92af6a34c4c06ec01a985c8902f94refs/remotes/origin/osmith/wipc792b8c79ee92af6a34c4c06ec01a985c8902f94c792b8c79ee92af6a34c4c06ec01a985c8902f94refs/remotes/origin/osmith/wip23926a2451a0ad3dd2f5e3179d64446d9d553a37016d6a2451a0ad3dd2f5e3179d64446d9d553a37016drefs/remotes/origin/master6a2451a0ad3dd2f5e3179d64446d9d553a37016d6a2451a0ad3dd2f5e3179d64446d9d553a37016drefs/remotes/origin/master538efe3cfcfb65a150604d6ee49f7b3540c44458538efe3cfcfb65a150604d6ee49f7b3540c44458origin/masterhttps://gerrit.osmocom.org/osmo-cifalse#303914064571408013osmocom-coverity #30393039falsefalse303954764SUCCESS1773094620663https://jenkins.osmocom.org/jenkins/view/TTCN3-asan/job/osmocom-coverity/3039/build5-deb12build-ansible- scripts/repo-install-test/run-inside.sh72c273eea130d63b1f7d21d4d717ed6f93eec9b51772715992000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.derepo-install-test: don't use deprecated apt-key
apt-key has been removed in debian 13, use "[signed-by=…]" instead.
Change-Id: I7b8b9336b16cceb7ece317c59de2f55ed404392e
2026-03-05 14:06:32 +010072c273eea130d63b1f7d21d4d717ed6f93eec9b5repo-install-test: don't use deprecated apt-keyeditscripts/repo-install-test/run-inside.sh
- scripts/repo-install-test/run-inside.sh15c6d06db698219838b95f15aa0dbab2f3228f561772794072000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.derepo-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
2026-03-06 11:47:52 +010015c6d06db698219838b95f15aa0dbab2f3228f56repo-install-test: fix test_conflict for debian 13editscripts/repo-install-test/run-inside.sh
- scripts/repo-install-test/run-inside.sha6c0607554039d7dbfacdc138c7103a0d7c364441772794072000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.derepo-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
2026-03-06 11:47:52 +0100a6c0607554039d7dbfacdc138c7103a0d7c36444repo-install-test: ignore sdcc-dbgsymeditscripts/repo-install-test/run-inside.sh
- scripts/repo-install-test/run-inside.shf36c16d94926f67d64e67e1f0cf0f62f3a167d4e1772794072000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.derepo-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
2026-03-06 11:47:52 +0100f36c16d94926f67d64e67e1f0cf0f62f3a167d4erepo-install-test: ignore charon-systemdeditscripts/repo-install-test/run-inside.sh
- scripts/repo-install-test/run-inside.shb96b5bba10c1a4a5806352ba13541c44d7c9068e1772794072000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.derepo-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
2026-03-06 11:47:52 +0100b96b5bba10c1a4a5806352ba13541c44d7c9068erepo-install-test: ignore pyhsseditscripts/repo-install-test/run-inside.sh
- ansible/roles/qemu/tasks/main.ymljobs/repo-install-test.ymlscripts/repo-install-test.shansible/roles/qemu/files/qemu-create-vms.shscripts/repo-install-test/run-inside.sh538efe3cfcfb65a150604d6ee49f7b3540c444581772794431000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.derepo-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
2026-03-06 11:53:51 +0100538efe3cfcfb65a150604d6ee49f7b3540c44458repo-install-test: run for debian 13 tooeditjobs/repo-install-test.ymleditscripts/repo-install-test.sheditansible/roles/qemu/tasks/main.ymleditansible/roles/qemu/files/qemu-create-vms.sheditscripts/repo-install-test/run-inside.sh
githttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith