From: sebastien <ml-dev@reycoyrehourcq.me>
To: guix-devel@gnu.org
Subject: Strange behavior using guix git authenticate
Date: Fri, 22 Nov 2024 18:24:34 +0000 [thread overview]
Message-ID: <173229987973.9.14827252628217822370.504261422@reycoyrehourcq.me> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 3592 bytes --]
Hi,
I try to follow the tutorial on guix blog (https://guix.gnu.org/en/blog/2024/authenticate-your-git-checkouts/) to authenticate my commit for a personal channel. I have some feedback to do, and possible missing info. for padawan like me.
- A / There are no information for pushing keyring branch to origin repo. Commit for keyring come before Introductory commit so pushing keyring to <yourforge> repository failed. Talking with ludovic, the tutorial doesn't say that pre-push hook need to be desactivated to push on <yourforge> repository.
- B / I follow the tutorial on an existing channel repo, two times, because i made some errors that imply : a reset --hard of the repo, the delete of the keyring branch, removing the authenticate line in git/config, removing the post-merge and pre-push hook. But, now my repository is probably in a strange state and guix git authenticate failed even if the commit is a correct descendant of the introductory commit. More info after :
An example with one commit after Introductory Commit (fcf50534c7fec17e689597cfaaec9f4cedb397de) :
---
commit 2eddf958be68a5a4df7fd43feb604707472f89a4 (HEAD -> master, origin/master)gpg: Signature faite le mar. 19 nov. 2024 23:05:17 CET
gpg: avec la clef RSA 41D051592D59A9C07AB4DF25DC55CB6B7043416E
gpg: Bonne signature de « xxx <xxx> » [ultime]
Author: xxx <xxx>
Date: Tue Nov 19 23:05:17 2024 +0100
add README
commit fcf50534c7fec17e689597cfaaec9f4cedb397de
gpg: Signature faite le mar. 19 nov. 2024 22:55:40 CET
gpg: avec la clef RSA 41D051592D59A9C07AB4DF25DC55CB6B7043416E
gpg: Bonne signature de « xxx <> » [ultime]
Author: xxx <>
Date: Tue Nov 19 22:55:40 2024 +0100
Introductory commit.
---
In my .git/config i have :
[core]repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = git@codeberg.org:reycoseb/extra-guix-channel.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
[guix "authentication"]
introduction-commit = fcf50534c7fec17e689597cfaaec9f4cedb397de
introduction-signer = 41D051592D59A9C07AB4DF25DC55CB6B7043416E
keyring = keyring
[branch "keyring"]
remote = origin
merge = refs/heads/keyring
I use a Yubikey with a specific subkey used to sign :
Signature key ....: 41D0 5159 2D59 A9C0 7AB4 DF25 DC55 CB6B 7043 416E created ....: 2020-09-01 12:13:40
Encryption key....: 04E1 4065 2E41 C847 4D7F B0EE D788 9EAF B20E C927
created ....: 2020-09-01 12:14:39
Authentication key: D57E C3C4 1288 E30D 17C1 290B 1DB9 AAD6 04D0 60C0
created ....: 2020-09-01 12:15:08
My .guix authorization file :
(authorizations (version 0) ;current file format version
(("41D0 5159 2D59 A9C0 7AB4 DF25 DC55 CB6B 7043 416E"
(name "xxx"))))
When i run guix git authenticate in my master branch, with yubikey activated, i have
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
Strange ? Also, the git push command say the same thing. If you have
I use guix 4c56d0c URL du dépôt : https://git.savannah.gnu.org/git/guix.git
branche : master
commit : 4c56d0cccdc44e12484b26332715f54768738c5f
Best regards,
Sebastien RC.
[-- Attachment #1.1.2.1: Type: text/html, Size: 9014 bytes --]
[-- Attachment #1.2: publickey - s.rey.coyrehourcq@proton.me - 0xC3237850.asc --]
[-- Type: application/pgp-keys, Size: 669 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next reply other threads:[~2024-11-23 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 18:24 sebastien [this message]
2024-11-27 18:39 ` Strange behavior using guix git authenticate Simon Tournier
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=173229987973.9.14827252628217822370.504261422@reycoyrehourcq.me \
--to=ml-dev@reycoyrehourcq.me \
--cc=guix-devel@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.
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).