unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 57306-done@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: bug#57306: guix pull to old commit fails due to unsupported manifest format
Date: Wed, 31 Aug 2022 13:06:20 +0200	[thread overview]
Message-ID: <87bks0brkj.fsf@gnu.org> (raw)
In-Reply-To: <87v8qaygzo.fsf@systemreboot.net> (Arun Isaac's message of "Tue,  30 Aug 2022 01:11:47 +0530")

Hi,

Arun Isaac <arunisaac@systemreboot.net> skribis:

>> I do not think it is related to guix-daemon and I think it is expected;
>> indeed it could be considered as a bug.  The command-line,
>>
>>     guix pull --commit=xyz -p /tmp/test
>>
>> writes /tmp/test/manifest using the current Guix (say manifest 4) and
>> not using Guix at commit xyz (say manifest 3).  Contrary to “guix
>> time-machine --commit=xyz”.
>
> Ah, that makes sense! Any ideas as to how this issue might be fixed?

I fixed it in 67a6828b2bb821274757f686f7c685b664339a96 using the same
trick as earlier.

Thanks!

Ludo’.




  reply	other threads:[~2022-08-31 11:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20  9:37 bug#57306: guix pull to old commit fails due to unsupported manifest format Arun Isaac
2022-08-20  9:40 ` paren--- via Bug reports for GNU Guix
2022-08-20  9:45   ` Arun Isaac
2022-08-20 10:23     ` paren--- via Bug reports for GNU Guix
2022-08-21  7:00 ` Josselin Poiret via Bug reports for GNU Guix
2022-08-29 19:37   ` Arun Isaac
2022-08-29 21:36     ` zimoun
2022-08-30 16:42       ` Arun Isaac
2022-08-30 17:20         ` zimoun
2022-08-29 14:59 ` zimoun
2022-08-29 19:41   ` Arun Isaac
2022-08-31 11:06     ` Ludovic Courtès [this message]
2022-08-31 13:15       ` zimoun
2022-09-01  7:42         ` Ludovic Courtès
2022-09-01  8:50           ` zimoun
2022-08-31 13:38       ` Arun Isaac

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=87bks0brkj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=57306-done@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    --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).