From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: A real-life test of long-term reproducibility
Date: Wed, 07 Sep 2022 17:39:41 +0200 [thread overview]
Message-ID: <m14jxjtcqq.fsf@fastmail.net> (raw)
In-Reply-To: <87y1uy40a4.fsf@gnu.org>
Hi Ludo and Simon,
> Sorry I replied to quickly; it should have been
> ‘--disable-authentication’.
>
> Why? Because here you’re trying to travel to a commit that’s not part
> of the “authenticated history”—that is, it’s not a descendant of the
> “introductory commit”, which is the first commit in history starting
> from which the “authentication invariant” holds.
>
> Hopefully this is clearer; maybe? :-)
It's perfectly clear. I just wonder how I would find the solution
starting from the error message.
zimoun <zimon.toutoune@gmail.com> writes:
>> And explain what it's about. I don't consider myself an absolute
>> beginner with Guix, but I don't understand what's going on here!
>
> Well, it is documented. ;-) The entry of ’time-machine’ [1] is the
> manual says:
...
Same remark: How would I get to that section of the manual from the
error message?
> I agree it could be improved. Any suggestion? :-)
My impression is that the error message I quoted is very specific to
this situation, so it could actually say "Retry with
--disable-authentication if you are sure that there is no security
issue". Right?
Cheers,
Konrad.
prev parent reply other threads:[~2022-09-07 16:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 8:43 A real-life test of long-term reproducibility Konrad Hinsen
2022-08-04 15:35 ` blake
2022-08-19 9:34 ` zimoun
2022-08-07 20:53 ` Ludovic Courtès
2022-08-08 5:21 ` Timothy Sample
2022-08-08 8:44 ` Konrad Hinsen
2022-08-19 10:25 ` zimoun
2022-08-22 11:34 ` Konrad Hinsen
2022-08-08 8:49 ` Konrad Hinsen
2022-09-02 13:17 ` Ludovic Courtès
2022-09-02 14:18 ` zimoun
2022-09-05 7:49 ` Konrad Hinsen
2022-09-05 9:32 ` zimoun
2022-09-05 9:51 ` Ludovic Courtès
2022-09-07 15:39 ` Konrad Hinsen [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=m14jxjtcqq.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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).