guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strange behavior using guix git authenticate


From: sebastien
Subject: Re: Strange behavior using guix git authenticate
Date: Wed, 27 Nov 2024 20:29:54 +0000

Hi Simon,

I'm feeling so stupid, sorry about that ... working late is never a good idea 
...

I redo the tutorial and now everything run fine, thanks \o/ !

There is also the "pre-push" hook to change a little because keyring cannot be 
validated :

git push -f --set-upstream origin keyring --no-verify

Best regards,
SR

Le mercredi 27 novembre 2024 à 7:39 PM, Simon Tournier 
<zimon.toutoune@gmail.com> a écrit :

> 

> 

> 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

Attachment: publickey - s.rey.coyrehourcq@proton.me - 0xC3237850.asc
Description: application/pgp-keys

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]