unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 56545-done@debbugs.gnu.org
Subject: bug#56545: guix time-machine/shell throws "unsupported manifest format" error
Date: Mon, 18 Jul 2022 07:04:25 -0400	[thread overview]
Message-ID: <87k08asmva.fsf@gmail.com> (raw)
In-Reply-To: <87h73f4jue.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 17 Jul 2022 21:31:21 +0200")

Hi Ludovic,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi!
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> scribes:
>
>> and the channels.scm file:
>>
>> (list (channel
>>        (inherit %default-guix-channel)
>>        (commit
>>         "ceeb2bfcaeb4380e01d26c8425e28b94ac13558a"))) ;2022-06-07
>>
>>
>> and was surprised to be greeted with the following error:
>>
>> (repl-version 0 1 1)
>> (exception %exception (non-self-quoting 140737300283024 "#<&message message: \"unsupported manifest format\">"))
>> /var/log/guix/drvs/j8/0wjfx7s7nxhcn0wjxfysnnv2knx0c1-guix-package-cache.drv (END)
>>
>> What does it mean?  Which manifest is it referring to?
>
> Commit 4ff12d1de7cd617b791996ee7ca1240660b4c20e introduced that bug,
> which was fixed in c9fbd40785a99e13a59d8e530830ce85220a9871:
>
>   https://issues.guix.gnu.org/56441
>
> ‘guix describe’ should show that you’re using a commit in that range.
>
> The solution is to run ‘time-machine’ from a commit outside that range,
> for instance with:
>
>   guix time-machine -- time-machine -C channels.scm -- whatever
>
> :-)

That's a happy resolution.  Thank you!

Maxim




      reply	other threads:[~2022-07-18 11:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  0:53 bug#56545: guix time-machine/shell throws "unsupported manifest format" error Maxim Cournoyer
2022-07-17 19:31 ` Ludovic Courtès
2022-07-18 11:04   ` Maxim Cournoyer [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=87k08asmva.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=56545-done@debbugs.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).