From: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Daniel Wagner <wagi@monom.org>
Subject: Re: [ANNOUNCE] 4.19.233-rt105
Date: Mon, 21 Mar 2022 11:13:07 +0100 [thread overview]
Message-ID: <20220321111307.20e45966@archlinux> (raw)
In-Reply-To: <20220321083611.ikxq26ax55nqavei@beryllium.lan>
On Mon, 21 Mar 2022 09:36:11 +0100, Daniel Wagner wrote:
>Did you import 587C5ECA5D0A306C.asc from korg?
Hi,
no, I imported it from a keyserver.
>I have very strong feelings when it comes to gpg and no they are not
>the good ones.
;)
I suspected a subkey, but OTOH it's odd that a check points to a
missing subkey, without mentioning the key that needs to be imported.
It's also odd that the needed key is available by a keyserver, but
without the subkey included.
Thank you, I imported from git and all is good now [1].
Regards,
Ralf
[1]
[rocketmouse@archlinux ~]$ gpg --import /tmp/pgpkeys/keys/587C5ECA5D0A306C.asc
gpg: key 587C5ECA5D0A306C: 17 signatures not checked due to missing keys
gpg: key 587C5ECA5D0A306C: "Daniel Wagner <wagi@monom.org>" 24 new signatures
gpg: key 587C5ECA5D0A306C: "Daniel Wagner <wagi@monom.org>" 2 new subkeys
gpg: Total number processed: 1
gpg: new subkeys: 2
gpg: new signatures: 24
[snip]
[rocketmouse@archlinux linux-rt]$ makepkg -s
==> Making package: linux-rt 4.19.235_rt106-0.1000 (Mon 21 Mar 2022 10:58:09 CET)
[snip]
==> Verifying source file signatures with gpg...
linux-4.19.235.tar ... Passed
patch-4.19.235-rt106.patch ... Passed
[snip]
prev parent reply other threads:[~2022-03-21 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 8:19 [ANNOUNCE] 4.19.233-rt105 Daniel Wagner
2022-03-18 5:01 ` Ralf Mardorf
2022-03-18 8:48 ` Daniel Wagner
[not found] ` <20220318102051.483333f2@archlinux>
2022-03-18 9:27 ` Ralf Mardorf
2022-03-18 9:45 ` Daniel Wagner
2022-03-18 17:00 ` Ralf Mardorf
2022-03-18 17:42 ` Ralf Mardorf
2022-03-21 8:36 ` Daniel Wagner
2022-03-21 10:13 ` Ralf Mardorf [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=20220321111307.20e45966@archlinux \
--to=ralf.mardorf@alice-dsl.net \
--cc=linux-rt-users@vger.kernel.org \
--cc=wagi@monom.org \
/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