From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Arun Isaac" <arunisaac@systemreboot.net>
Cc: 57306-done@debbugs.gnu.org
Subject: bug#57306: guix pull to old commit fails due to unsupported manifest format
Date: Wed, 31 Aug 2022 15:15:47 +0200 [thread overview]
Message-ID: <86zgfkblks.fsf@gmail.com> (raw)
In-Reply-To: <87bks0brkj.fsf@gnu.org>
Hi Ludo,
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? Well, I miss when or
where version 4 is used then.
--8<---------------cut here---------------start------------->8---
$ for i in $(seq 4 9); \
do
grep -A 5 '(manifest' \
/var/guix/profiles/per-user/simon/current-guix-$i-link/manifest \
;done
(manifest
(version 3)
(packages
(("guix"
"06493e7"
"out"
(manifest
(version 4)
(packages
(("guix"
"8f0d45c"
"out"
(manifest
(version 4)
(packages
(("guix"
"65cabb0"
"out"
(manifest
(version 4)
(packages
(("guix"
"67a6828"
"out"
(manifest
(version 3)
(packages
(("guix"
"0bb0e84"
"out"
(manifest
(version 3)
(packages
(("guix"
"23152ff"
"out"
--8<---------------cut here---------------end--------------->8---
From my understanding, set #:format-version to 3 should only be
considered when <hash> is a parent/ancestor of current commit in
’--commit=<hash>’.
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. :-)
I think version 3 should be only used when the option --allow-downgrades
is provided.
Cheers,
simon
next prev parent reply other threads:[~2022-08-31 13:20 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 [this message]
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=86zgfkblks.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=57306-done@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--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).