unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>, help-guix@gnu.org
Subject: Re: guix pull: error: commit 3946540 not signed by an authorized key: 2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0
Date: Sat, 06 Aug 2022 13:43:25 -0700	[thread overview]
Message-ID: <87pmhd5cia.fsf@contorta> (raw)
In-Reply-To: <6ced36e803643a57299590c72ebce003@tobias.gr>

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

On 2022-08-06, Tobias Geerinckx-Rice wrote:
> On 2022-08-06 20:48, Tobias Geerinckx-Rice wrote:
>>   guix pull: error: commit 39465409f0481f27d252ce25d2b02d3f5cbc6723
>>   not signed by an authorized key:
>>   2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0
>
> I tried a few other random things to wriggle out of this but I think 
> we're stuck (which is, design-wise, probably a good thing).

What a great opportunity to switch to using "main" instead of "master"
anyways. :)

I thought git was going to at some point make "main" the default new
branch name instead of "master" anyways. May as well get ahead of the
game, now that there's a technical reason to consider switching branch
names anyways.

live well,
  vagrant

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

  reply	other threads:[~2022-08-06 20:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 18:48 guix pull: error: commit 3946540 not signed by an authorized key: 2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0 Tobias Geerinckx-Rice
2022-08-06 19:32 ` Tobias Geerinckx-Rice
2022-08-06 20:43   ` Vagrant Cascadian [this message]
2022-08-06 21:06     ` Tobias Geerinckx-Rice
2022-08-06 21:09       ` Tobias Geerinckx-Rice
2022-08-09 20:56     ` Renaming ‘master’ to ‘main’ Ludovic Courtès
2022-08-09 22:01       ` Felix Lechner
2022-08-09 23:05       ` Felix Lechner via
2022-08-10  6:28       ` blake

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=87pmhd5cia.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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).