From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Luis Guillermo Vázquez de Lara Cisneros" <lgvazdela@yahoo.com.mx>
Cc: git@vger.kernel.org
Subject: Re: error ubuntu 22.04
Date: Sun, 15 Sep 2024 15:37:58 +0000 [thread overview]
Message-ID: <Zub_Vi9bcgSCodEV@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <ec8a1a28-2e16-4e4d-8329-eae6fabd22ab@yahoo.com.mx>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
On 2024-09-15 at 14:44:44, Luis Guillermo Vázquez de Lara Cisneros wrote:
> Dear Sirs:
Hey,
I might suggest just omitting this greeting here or using something
informal like "Hi". We're not all men or "sir", and this is a
relatively informal and collegial list.
> When updating my system (ubuntu 22.04), I recently started to receive the
> following message:
>
> Fallo al obtener https://cli.github.com/packages/dists/stable/InRelease Las
> siguientes firmas no fueron válidas: EXPKEYSIG 23F3D4EA75716059 GitHub CLI
> <opensource+cli@github.com>
>
> How can I solve this?
This is about the GitHub CLI. The Git project isn't affiliated with
GitHub or any other forge, so this isn't really on topic here.
However, I happen to be aware that the GitHub CLI rotated the OpenPGP
keys they use to sign their packages recently and you can see
https://github.com/cli/cli/issues/9569 for more details. Hopefully
that's helpful and if you need more assistance, the GitHub CLI team
should be able to help.
--
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2024-09-15 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ec8a1a28-2e16-4e4d-8329-eae6fabd22ab.ref@yahoo.com.mx>
2024-09-15 14:44 ` error ubuntu 22.04 Luis Guillermo Vázquez de Lara Cisneros
2024-09-15 15:37 ` brian m. carlson [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=Zub_Vi9bcgSCodEV@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=lgvazdela@yahoo.com.mx \
/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