unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 41908-done@debbugs.gnu.org
Subject: bug#41908: guix time-machine fails; XXXX is not related to introductory commit of channel 'guix'
Date: Tue, 23 Jun 2020 09:35:59 +0200	[thread overview]
Message-ID: <87d05q5j4w.fsf@gnu.org> (raw)
In-Reply-To: <86imfjsco3.fsf@gmail.com> (zimoun's message of "Mon, 22 Jun 2020 10:54:52 +0200")

Hi Simon,

zimoun <zimon.toutoune@gmail.com> skribis:

> $ /tmp/c/bin/guix time-machine --commit=36640207c9 -- help
> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
> Usage: guix COMMAND ARGS...
>
> $ cat ~/.cache/guix/authentication/channels/guix
> ;; List of previously-authenticated commits.
>
> ("41a2d6a8b9294a6eb8e97aaefd569e755f5f461e"
>  "e70e097882699865f63eabc5fb29b4fe4468a97b")
>
>
> However, the commit 36640207c9 is not considered as authenticated,
> right?  So, the older authenticated commit is the first commit used by
> time-machine, right?

Note that it’s the closure of the commits listed in the cache that’s
considered authenticated.  So not every commit is listed.

Does that make sense?

Ludo’.




  reply	other threads:[~2020-06-23  7:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17  9:27 bug#41908: guix time-machine fails; XXXX is not related to introductory commit of channel 'guix' Jan Nieuwenhuizen
2020-06-18 22:29 ` zimoun
2020-06-18 23:02   ` zimoun
2020-06-19 21:17 ` Ludovic Courtès
2020-06-19 23:22   ` zimoun
2020-06-20 10:40     ` Ludovic Courtès
2020-06-21 16:17       ` zimoun
2020-06-22  8:01         ` Ludovic Courtès
2020-06-20 13:58   ` Marius Bakke
2020-06-21 15:43   ` Ludovic Courtès
2020-06-21 16:18     ` zimoun
2020-06-22  8:54     ` zimoun
2020-06-23  7:35       ` Ludovic Courtès [this message]
2020-06-23  8:42         ` zimoun
2020-06-23  8:53           ` Ludovic Courtès

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=87d05q5j4w.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41908-done@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).