Skip to content

Changes

Started by upstream project update-osmo-ci-on-slaves #3267
Started 1 day 1 hr ago
Queued 4 ms
Took 7.1 sec on simtester

Summary

  1. repo-install-test: test osmo-pfcp-tool in latest (details)
  2. repo-install-test: debian 10: osmo-gbproxy only (details)
Commit 598cca7438f22be3e0712e7a097a274fc9467792 by Oliver Smith
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
The file was modifiedscripts/repo-install-test/run-inside.sh
Commit 886be7413ad26bfe9c4562f4d2c5fc2a791fbae5 by Oliver Smith
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
The file was modifiedscripts/repo-install-test/run-inside.sh