From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 64187@debbugs.gnu.org
Subject: bug#64187: guix locate: unsupported manifest format
Date: Fri, 07 Jul 2023 16:03:37 +0200 [thread overview]
Message-ID: <87h6qfkedi.fsf@gnu.org> (raw)
In-Reply-To: <87mt0ctd2e.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 04 Jul 2023 08:16:31 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> However, how can it happen? ‘guix locate’ knows all the manifest format
>> version, so maybe it mistook a file for a manifest when in fact it’s
>> something else?
>>
>> Could you ‘strace -o /tmp/log.strace guix locate ls’ to get the name of
>> the offending file for now?
>
> The last manifest it reads is
> /gnu/var/guix/profiles/per-user/wneuber/guix-profile-1-link/manifest
> with the following contents
>
> (manifest
> (version 1)
> (packages
> (("gcc"
> "4.9.2"
> "out"
> "/gnu/store/ym7sybrdifnm3g0rafhclv891niaczcv-gcc-4.9.2"
> ()))))
Woow, this profile predates May 2015 and commit
dedb17ad010ee9ef67f3f4f3997dd17f226c8090. And indeed, it’s no longer
recognized since e7e04396c0e91569bf493e1352d6539babc15327 (July 2022).
I’ll work on a fix…
Ludo’.
next prev parent reply other threads:[~2023-07-07 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 7:25 bug#64187: guix locate: unsupported manifest format Ricardo Wurmus
2023-06-21 14:41 ` Ludovic Courtès
2023-07-04 6:16 ` Ricardo Wurmus
2023-07-07 14:03 ` Ludovic Courtès [this message]
2023-07-11 16:22 ` Ludovic Courtès
2023-07-13 6:46 ` Ricardo Wurmus
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=87h6qfkedi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=64187@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).