unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: help-guix@gnu.org
Subject: Channel authentication: missing keyring branch
Date: Sat, 11 Jul 2020 12:46:33 +0200	[thread overview]
Message-ID: <87blkmqqgm.fsf@ambrevar.xyz> (raw)

[-- Attachment #1: Type: text/plain, Size: 470 bytes --]

Hi!

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.
Besides, is there a convenient way to create the keyring branch and
populate it with the public keys of all the committers so far?

Cheers!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

             reply	other threads:[~2020-07-11 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 10:46 Pierre Neidhardt [this message]
2020-07-24 16:26 ` Channel authentication: missing keyring branch Ludovic Courtès
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=87blkmqqgm.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --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).