From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 1/1] meta: Update debian ports signing key
Date: Fri, 4 Feb 2022 10:15:21 +0100 [thread overview]
Message-ID: <20220204091521.32195-2-ubely@ilbers.de> (raw)
In-Reply-To: <20220204091521.32195-1-ubely@ilbers.de>
Replace expired Debian Ports Archive Automatic Signing Key (2021)
(ID:5A88D659DCB811BB) by new Debian Ports Archive Automatic Signing Key
(2022) (ID: E852514F5DF312F6) to make debian-sid-ports targets work.
Also added Debian Ports Archive Automatic Signing Key (2023)
(ID:B523E5F3FC4E5F2C) in advance. It will be used for signing
starting from 2023 Feb 01.
Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
meta/conf/distro/debian-sid-ports.conf | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/meta/conf/distro/debian-sid-ports.conf b/meta/conf/distro/debian-sid-ports.conf
index 32bd32f3..e71a467d 100644
--- a/meta/conf/distro/debian-sid-ports.conf
+++ b/meta/conf/distro/debian-sid-ports.conf
@@ -10,15 +10,16 @@ BASE_DISTRO_CODENAME = "sid"
HOST_DISTRO ?= "debian-sid"
-DEBIAN_PORTS_KEY = "https://www.ports.debian.org/archive_2021.key;sha256sum=44a0c59cac5385cd0a1506f695fbd2381fb71a04d8afc05248ad00a0ec6052aa"
+DEBIAN_PORTS_KEYS += "https://www.ports.debian.org/archive_2022.key;sha256sum=213531906f80d79a5dbc8573f57f2a2831b71383cc2d568feba97bb4db94adcc"
+DEBIAN_PORTS_KEYS += "https://www.ports.debian.org/archive_2023.key;sha256sum=cd29cb45654c2d31e8c56c6215838bd7e2d29612021ab04486109e82175a0a98"
DISTRO_APT_SOURCES = "conf/distro/debian-${BASE_DISTRO_CODENAME}-ports.list"
-DISTRO_BOOTSTRAP_KEYS += "${DEBIAN_PORTS_KEY}"
+DISTRO_BOOTSTRAP_KEYS += "${DEBIAN_PORTS_KEYS}"
DISTRO_CONFIG_SCRIPT ?= "debian-configscript.sh"
DISTRO_KERNELS ?= "riscv64"
HOST_DISTRO_APT_SOURCES += "${DISTRO_APT_SOURCES}"
-THIRD_PARTY_APT_KEYS += "${DEBIAN_PORTS_KEY}"
+THIRD_PARTY_APT_KEYS += "${DEBIAN_PORTS_KEYS}"
IMAGE_PREINSTALL += "init"
--
2.20.1
next prev parent reply other threads:[~2022-02-04 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 9:15 [PATCH v2 0/1] Update expired " Uladzimir Bely
2022-02-04 9:15 ` Uladzimir Bely [this message]
2022-02-16 7:52 ` Anton Mikanovich
2023-02-01 10:54 [PATCH v2 1/1] meta: Update " Felix Moessbauer
2023-02-01 11:36 ` Jan Kiszka
2023-02-01 14:04 ` Moessbauer, Felix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220204091521.32195-2-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox