public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/1] Update expired debian ports signing key
Date: Wed, 16 Feb 2022 10:52:17 +0300	[thread overview]
Message-ID: <515f82f3-6138-e907-8957-ac75d8dce90b@ilbers.de> (raw)
In-Reply-To: <20220204091521.32195-1-ubely@ilbers.de>

04.02.2022 12:15, Uladzimir Bely wrote:
> 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(-)
>
Applied to next, thanks.


      parent reply	other threads:[~2022-02-16  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04  9:15 Uladzimir Bely
2022-02-04  9:15 ` [PATCH v2 1/1] meta: Update " Uladzimir Bely
2022-02-16  7:52 ` Anton Mikanovich [this message]

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=515f82f3-6138-e907-8957-ac75d8dce90b@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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