osmith has uploaded this change for review.

View Change

OBS: add the new osmocom-keyring package

The public key for OBS packages needs to be extended every two years.
When the previous key expires, it is not possible to update packages
anymore until users replace the old key with the new, extended key.

To make this less inconvenient for users, introduce a new
osmocom-keyring package that holds the current key (valid for 2 years),
which will get updated every year with an extended key (valid for
another 2 years, I'll add a jenkins job to remind us). This means as
long as users upgrade their packages once a year, they will
automatically receive the new key.

Related: https://gitea.osmocom.org/osmocom/osmocom-keyring
Related: OS#6567
Change-Id: I370b4fa0c6f7e8a925b1ddd7c1c47980a8f4fea2
---
M scripts/obs/lib/config.py
1 file changed, 2 insertions(+), 0 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/28/40428/1

diff --git a/scripts/obs/lib/config.py b/scripts/obs/lib/config.py
index dc67757..4d8bcd3 100644
--- a/scripts/obs/lib/config.py
+++ b/scripts/obs/lib/config.py
@@ -47,6 +47,8 @@
 # NOTE: Consider whether new packages should be added to EXCLUDE_PACKAGES in
 #       osmocom-obs-nightly-asan.yml.
 projects_osmocom = [
+    "osmocom-keyring",
+
     "erlang/osmo_dia2gsup",
     "erlang/osmo-epdg",
     "erlang/osmo-s1gw",

To view, visit change 40428. To unsubscribe, or for help writing mail filters, visit settings.