From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Channel authentication: missing keyring branch
Date: Fri, 24 Jul 2020 18:26:55 +0200 [thread overview]
Message-ID: <878sf86fqo.fsf@gnu.org> (raw)
In-Reply-To: <87blkmqqgm.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sat, 11 Jul 2020 12:46:33 +0200")
Hi,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> I recently added authentication to a Guix channel.
> On Guix pull, guix complained that the remote has no `keyring' branch.
> Indeed, creating an orphan `keyring' branch with all the public keys
> stored in it worked.
>
> This does not seems to be documented in the manual.
Oops, it’ll show up soon at:
https://guix.gnu.org/manual/devel/en/html_node/Channels.html#Specifying-Channel-Authorizations
> Besides, is there a convenient way to create the keyring branch and
> populate it with the public keys of all the committers so far?
No, but I guess you could take the output of ‘git shortlog -s --email’
and pass it to ‘gpg --export’ & co.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-07-24 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 10:46 Channel authentication: missing keyring branch Pierre Neidhardt
2020-07-24 16:26 ` Ludovic Courtès [this message]
2020-07-24 16:51 ` Pierre Neidhardt
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=878sf86fqo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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).