From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 0/1] Update expired debian ports signing key
Date: Fri, 4 Feb 2022 10:15:20 +0100 [thread overview]
Message-ID: <20220204091521.32195-1-ubely@ilbers.de> (raw)
On Feb 01 we got debootstrap error for debian-sid-ports-riscv64:
E: Release signed by unknown key (key id E852514F5DF312F6)
It looks like this repo every year changes the key to sign releases.
Also, once a year a new key is generated to be used for signing
in the future:
year : --2021----|----2022----|----2023----|----2024--
key created: ---------C|-*---------D|-----------E|----------
signing key: AAAAAAAAAA ABBBBBBBBBBB BCCCCCCCCCCC CDDDDDDDDD
This change allows to have 2 keys for debian-sid-ports: one is
currently used, and another is for smooth transition through
the date of signing key change.
Changes since v1:
- Added a key for 2023 year in advance
Uladzimir Bely (1):
meta: Update debian ports signing key
meta/conf/distro/debian-sid-ports.conf | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2022-02-04 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 9:15 Uladzimir Bely [this message]
2022-02-04 9:15 ` [PATCH v2 1/1] meta: Update " Uladzimir Bely
2022-02-16 7:52 ` [PATCH v2 0/1] Update expired " Anton Mikanovich
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-1-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