From: David Gibson <david@gibson.dropbear.id.au>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>, b@yekko
Cc: keys@linux.kernel.org
Subject: Re: New key
Date: Fri, 24 Feb 2023 15:21:12 +1100 [thread overview]
Message-ID: <Y/g7OAJShy0chmQj@yekko> (raw)
In-Reply-To: <Y/g3dB5RZq7bqmu9@yekko>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Fri, Feb 24, 2023 at 03:05:08PM +1100, David Gibson wrote:
> On Thu, Feb 23, 2023 at 11:19:25AM -0500, Konstantin Ryabitsev wrote:
> > On Wed, Feb 22, 2023 at 02:42:49PM +1100, David Gibson wrote:
> > > > Please resend the key (as a follow-up to this message is fine). Keyservers are
> > > > not reliable these days, unfortunately.
> > >
> > > Ok, included below.
> >
> > I have added your new key to the pgpkeys.git.
>
> Great, thanks.
I tried to kup a new dtc release signed with the new key, and it's
still failing. Is there some extra step that's needed?
$ kup -v put ../dtc-1.7.0.tar.gz ../dtc-1.7.0.tar.sign /pub/software/utils/dtc/dtc-1.7.0.tar.gz
DATA 209620 gz
SIGN 833 %
PUT /pub/software/utils/dtc/dtc-1.7.0.tar.gz
FATAL: Signature invalid
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-24 4:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 10:53 New key David Gibson
2023-02-09 20:41 ` Konstantin Ryabitsev
2023-02-10 0:06 ` David Gibson
[not found] ` <Y+mh9AALS6uCC/0A@yekko>
2023-02-21 22:28 ` Konstantin Ryabitsev
2023-02-22 3:42 ` David Gibson
2023-02-23 16:19 ` Konstantin Ryabitsev
2023-02-24 4:05 ` David Gibson
2023-02-24 4:21 ` David Gibson [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-14 15:30 Konrad Dybcio
2023-04-17 16:35 ` Konstantin Ryabitsev
2023-05-09 9:51 Konrad Dybcio
2023-05-09 18:49 ` Konstantin Ryabitsev
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=Y/g7OAJShy0chmQj@yekko \
--to=david@gibson.dropbear.id.au \
--cc=b@yekko \
--cc=keys@linux.kernel.org \
--cc=konstantin@linuxfoundation.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