From: Marcel van der Boom <marcel@hsdev.com>
To: help-guix@gnu.org
Subject: Re: Authenticate a channel
Date: Sun, 29 Dec 2024 14:04:59 +0100 [thread overview]
Message-ID: <6f5ae1ff-a5fa-4c82-9cd2-54d38daa4c0b@hsdev.com> (raw)
In-Reply-To: <87ed1ru1nv.fsf@gnu.org>
I have issues with this too. On every git pull and guix pull I get
messages that my key is missing, although I did add it locally to the
keyring branch.
Is there a procedure documented somewhere on how to make sure the
signature is present and correct? It feels like I am just missing
something small here.
Some unknowns for me:
- are subkeys supported? anything special needed?
- it seems there is a file-naming convention on the keyring branch for
the keys?
- do i need to pull the keyring in manually over time of does the
machinery take care of this?
On 2024-12-28 19:01, Ludovic Courtès wrote:
> Hi Jérémy,
>
> Jeremy Korwin-Zmijowski <jeremy@korwin-zmijowski.fr> skribis:
>
>> I haven't change anything with my keys since then. So I was surprised
>> to see `guix pull` returning :
>>
>> guix pull: erreur : could not authenticate commit
>> ad4cea635090b30d259dcf1cb690f07c831f6a1e: key EFBB 9626 457A C7F6
>> FAED FA70 A2E0 F15D BF8E A5F0 is missing
>
> Presumably this indicate that this key is missing from the ‘keyring’
> branch of your channel. You should export it and add it to that branch.
>
> HTH!
>
> Ludo’.
>
next prev parent reply other threads:[~2024-12-30 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 16:48 Authenticate a channel Jeremy Korwin-Zmijowski
2024-12-28 18:01 ` Ludovic Courtès
2024-12-29 13:04 ` Marcel van der Boom [this message]
2024-12-30 18:57 ` Cayetano Santos
2025-01-01 12:03 ` Marek Paśnikowski
2025-01-02 9:07 ` Jeremy Korwin-Zmijowski
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6f5ae1ff-a5fa-4c82-9cd2-54d38daa4c0b@hsdev.com \
--to=marcel@hsdev.com \
--cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).