From: Cayetano Santos <csantosb@inventati.org>
To: Marcel van der Boom <marcel@hsdev.com>
Cc: help-guix@gnu.org
Subject: Re: Authenticate a channel
Date: Mon, 30 Dec 2024 19:57:55 +0100 [thread overview]
Message-ID: <875xn1nglo.fsf@inventati.org> (raw)
In-Reply-To: <6f5ae1ff-a5fa-4c82-9cd2-54d38daa4c0b@hsdev.com> (Marcel van der Boom's message of "Sun, 29 Dec 2024 14:04:59 +0100")
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
>dim. 29 déc. 2024 at 14:04, Marcel van der Boom <marcel@hsdev.com> wrote:
> 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.
Most up to date documentation is here,
https://guix.gnu.org/manual/devel/en/html_node/Specifying-Channel-Authorizations.html
> 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?
Have you checked with other public channels ?
--
Cayetano Santos
GnuPG Key: https://meta.sr.ht/~csantosb.pgp
FingerPrint: CCB8 1842 F9D7 058E CD67 377A BF5C DF4D F6BF 6682
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2024-12-30 18:58 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
2024-12-30 18:57 ` Cayetano Santos [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xn1nglo.fsf@inventati.org \
--to=csantosb@inventati.org \
--cc=help-guix@gnu.org \
--cc=marcel@hsdev.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.