On Tue, 17 Jan 2023 23:18:13 +0800, Ludovic Courtès wrote: > > Hi, > > Hilton Chain <hako@ultrarare.space> skribis: > > > I encountered the issue when adding a new key to my Guix channel. Though I > > haven't figured out what happened exactly, I'm currently able to reproduce > > the > > issue with the following steps. > > Fishy. Would you be able to write a script to reproduce the whole > scenario? That’d make it easier to test and we’d be sure we’re talking > about the same thing. > > Thanks for reporting it! > > Ludo’.
I created a git repository and uploaded it to GitHub: <https://github.com/rakino/bug-60852> Outputs: : gpg: key 8FDEAEDC3B8C0109: public key "Key One" imported : gpg: key 8FDEAEDC3B8C0109: secret key imported : gpg: Total number processed: 1 : gpg: imported: 1 : gpg: secret keys read: 1 : gpg: secret keys imported: 1 : gpg: key FC92800E84F3F3B6: public key "Key Two" imported : gpg: key FC92800E84F3F3B6: secret key imported : gpg: Total number processed: 1 : gpg: imported: 1 : gpg: secret keys read: 1 : gpg: secret keys imported: 1 : [trunk 083b7ef] Authorize Key One. : 1 file changed, 4 insertions(+) : create mode 100644 .guix-authorizations : [trunk 1602009] Authorize Key Two. : 1 file changed, 3 insertions(+), 1 deletion(-) : [trunk 732579e] Test. : 1 file changed, 1 insertion(+) : create mode 100644 dummy : Authenticating commits 083b7ef to 732579e (2 new commits)... : [####################################### ]guix git: error: commit 732579e0f0dc6d15dbd2ea6826e01ae3aaf999a4 not signed by an authorized key: E1B1 7BEA 095F 5B25 4135 F6D1 F820 25E7 800B 3CCF : HEAD is now at 083b7ef Authorize Key One. : [trunk af4fae1] Authorize Key Two. : 1 file changed, 2 insertions(+) : [trunk 4b90546] Test. : 1 file changed, 1 insertion(+) : create mode 100644 dummy : Authenticating commits 083b7ef to 4b90546 (2 new commits)... : HEAD is now at 0ba5461 Add start.sh.
