From: Simon Tournier <zimon.toutoune@gmail.com>
To: sebastien <ml-dev@reycoyrehourcq.me>, guix-devel@gnu.org
Subject: Re: Strange behavior using guix git authenticate
Date: Wed, 27 Nov 2024 19:39:33 +0100 [thread overview]
Message-ID: <87zflkh66y.fsf@gmail.com> (raw)
In-Reply-To: <173229987973.9.14827252628217822370.504261422@reycoyrehourcq.me>
Hi Sébastien,
On Fri, 22 Nov 2024 at 18:24, sebastien <ml-dev@reycoyrehourcq.me> wrote:
> Authentification des commits fcf5053 à 2eddf95 (1 nouveaux commits)...guix git: erreur : commit 2eddf958be68a5a4df7fd43feb604707472f89a4 not signed by an authorized key: 41D0 5159 2D59 A9C0 7AB4 DF25 DC55 CB6B 7043 416E
If we speak about [1], I think the mistake comes from a typo in the
name: ’s’ instead of ’z’.
.guix-authorisations -> .guix-authorizations
Because of that, the procedure ’commit-authorized-keys’ returns an empty
list.
Renaming, does it fix your issue?
That’s said, maybe we could improve the UI by checking these two
requirements for authorization: a file name ’.guix-authorizations’ and a
branch ’keyring’ (although ’keyring’ is a key passed around).
Cheers,
simon
1: https://gitlab.huma-num.fr/gt-notebook/workshop/je_notebook_2024/atelier-bdc-notebooks/gt-guix-doc-channel/-/blob/f0d0930d00afdb62544f15ad69cac1be776ef7bc/.guix-authorisations
next prev parent reply other threads:[~2024-11-27 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 18:24 Strange behavior using guix git authenticate sebastien
2024-11-27 18:39 ` Simon Tournier [this message]
2024-11-27 20:29 ` sebastien via Development of GNU Guix and the GNU System distribution.
2024-11-27 22:12 ` Attila Lendvai
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=87zflkh66y.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ml-dev@reycoyrehourcq.me \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).