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: Arun Isaac <arunisaac@systemreboot.net>, 57306-done@debbugs.gnu.org
Subject: bug#57306: guix pull to old commit fails due to unsupported manifest format
Date: Thu, 01 Sep 2022 09:42:00 +0200	[thread overview]
Message-ID: <87y1v37d87.fsf@gnu.org> (raw)
In-Reply-To: <86zgfkblks.fsf@gmail.com> (zimoun's message of "Wed, 31 Aug 2022 15:15:47 +0200")

Hi,

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

> On Wed, 31 Aug 2022 at 13:06, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> I fixed it in 67a6828b2bb821274757f686f7c685b664339a96 using the same
>> trick as earlier.
>
> It means version 3 is used all the time, right?

Yes.

> Well, I miss when or where version 4 is used then.

Generations that were created with a slightly older Guix have a
version-4 manifest.

> From my understanding, set #:format-version to 3 should only be
> considered when <hash> is a parent/ancestor of current commit in
> ’--commit=<hash>’.

Here #:format-version 3 is unconditional.  That avoids having to make
assumptions about whether or not the target commit understands newer
format versions.

But you’re right: a refinement would be to use version 3 only when
targeting an ancestor.  I don’t think it’s worth the trouble though.

> Well, I do not remember all the discussion about --allow-downgrades.
> For instance, why is
>
>      $ guix pull --commit=6f75565b -p /tmp/test
>
> not complaining about downgrade?  Because it is a downgrade. :-)

Whether it’s a downgrade depends on what’s in /tmp/test when you run it.

Thanks,
Ludo’.




  reply	other threads:[~2022-09-01  8:14 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
2022-08-31 13:15       ` zimoun
2022-09-01  7:42         ` Ludovic Courtès [this message]
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=87y1v37d87.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).