From: Julien Lepiller <julien@lepiller.eu>
To: guix-science@gnu.org, Konrad Hinsen <konrad.hinsen@fastmail.net>
Subject: Re: Help! I messed up guix-past
Date: Fri, 09 Sep 2022 18:16:08 +0200 [thread overview]
Message-ID: <C467C175-664F-4BA3-8B4E-999055A19E9B@lepiller.eu> (raw)
In-Reply-To: <m1mtb87f3r.fsf@fastmail.net>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
The guix repo has a pre-push hook you could take as inspiration. It could prevent you from pushing unsigned/unauthorized commits by mistake.
Le 9 septembre 2022 17:16:24 GMT+02:00, Konrad Hinsen <konrad.hinsen@fastmail.net> a écrit :
>Hi everyone,
>
>I added a few packages to guix-past, but apparently forgot something
>because I cannot pull without –disable-authentication. The error message
>is
>
>guix pull: error: commit e9ccdb84d688c19415610474e8e630b72248c380 lacks a signature
>
>Two questions:
> - How can I fix this?
> - What should I have done to prevent this? Probably sign my commits,
> but is that enough? With nobody knowing my key, signing is probably not
> worth much on its own.
>
>Cheers,
> Konrad
>
[-- Attachment #2: Type: text/html, Size: 1025 bytes --]
prev parent reply other threads:[~2022-09-09 16:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 15:16 Help! I messed up guix-past Konrad Hinsen
2022-09-09 15:36 ` Ricardo Wurmus
2022-09-09 15:46 ` zimoun
2022-09-09 16:10 ` Konrad Hinsen
2022-09-09 17:39 ` zimoun
2022-09-10 7:39 ` Konrad Hinsen
2022-09-10 9:47 ` zimoun
2022-09-10 16:20 ` Konrad Hinsen
2022-09-11 14:07 ` Ludovic Courtès
2022-09-11 15:19 ` Efraim Flashner
2022-09-12 6:16 ` Konrad Hinsen
2022-09-12 15:26 ` Ludovic Courtès
2022-09-13 8:58 ` Konrad Hinsen
2022-09-13 9:23 ` Ricardo Wurmus
2022-09-14 9:31 ` Konrad Hinsen
2022-09-10 10:27 ` Ludovic Courtès
2022-09-10 10:40 ` zimoun
2022-09-10 14:39 ` Ricardo Wurmus
2022-09-12 16:00 ` zimoun
2022-09-09 16:16 ` Julien Lepiller [this message]
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=C467C175-664F-4BA3-8B4E-999055A19E9B@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-science@gnu.org \
--cc=konrad.hinsen@fastmail.net \
/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).