From: Uladzimir Bely <ubely@ilbers.de>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta: Update debian ports signing keys
Date: Tue, 23 Jan 2024 13:07:33 +0300 [thread overview]
Message-ID: <91c587e38f93b4be399cbd3b4c100b128dcb0fe5.camel@ilbers.de> (raw)
In-Reply-To: <acdf39651f6de71ec907d4bf13ede825ff01f587.camel@siemens.com>
On Tue, 2024-01-23 at 09:03 +0000, MOESSBAUER, Felix wrote:
> On Tue, 2024-01-23 at 09:14 +0100, Uladzimir Bely wrote:
> > 1. Remove 2022 key.
> >
> > 2. Add Debian Ports Archive Automatic Signing Key (2025)
> > (ID: 3AF65F93D6FBC5B9) in advance. It will be used for signing
> > starting from 2045 Feb 01.
> ------------------^
>
> I guess this should be 2025. This can be fixed while merging.
>
> Felix
>
Thanks, it's a typo. Will fix it while merging to next.
> >
> > These changes are made in sync with the debian-ports-archive-
> > keyring,
> > version 2024.01.05 package.
> >
> > Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> > ---
> > meta/conf/distro/debian-sid-ports.conf | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/conf/distro/debian-sid-ports.conf
> > b/meta/conf/distro/debian-sid-ports.conf
> > index 8a0b3a98..f045a3f2 100644
> > --- a/meta/conf/distro/debian-sid-ports.conf
> > +++ b/meta/conf/distro/debian-sid-ports.conf
> > @@ -10,9 +10,9 @@ BASE_DISTRO_CODENAME = "sid"
> >
> > HOST_DISTRO ?= "debian-sid"
> >
> > -DEBIAN_PORTS_KEYS +=
> > "
> > https://www.ports.debian.org/archive_2022.key;sha256sum=213531906f80
> > d79a5dbc8573f57f2a2831b71383cc2d568feba97bb4db94adcc"
> > DEBIAN_PORTS_KEYS +=
> > "
> > https://www.ports.debian.org/archive_2023.key;sha256sum=a29b938b9f30
> > 2dc7386cc77a743f50b1fe2a55eb17a9a22db938492047f59f3f"
> > DEBIAN_PORTS_KEYS +=
> > "
> > https://www.ports.debian.org/archive_2024.key;sha256sum=d7c297ea226b
> > b685ac68195d0b61078f8964a611136b11b9514babfa3b92c448"
> > +DEBIAN_PORTS_KEYS +=
> > "
> > https://www.ports.debian.org/archive_2025.key;sha256sum=2a729612c514
> > fac719d142910b1d876c7abecba00df51f2b32041d530aeb41d6"
> >
> > DISTRO_APT_SOURCES = "conf/distro/debian-${BASE_DISTRO_CODENAME}-
> > ports.list"
> > DISTRO_BOOTSTRAP_KEYS += "${DEBIAN_PORTS_KEYS}"
> > --
> > 2.20.1
> >
>
> --
> Siemens AG, Technology
> Linux Expert Center
>
>
next prev parent reply other threads:[~2024-01-23 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 8:14 Uladzimir Bely
2024-01-23 9:03 ` MOESSBAUER, Felix
2024-01-23 10:07 ` Uladzimir Bely [this message]
2024-01-26 7:39 ` Uladzimir Bely
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=91c587e38f93b4be399cbd3b4c100b128dcb0fe5.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--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