GNU bug report logs - #64187
guix locate: unsupported manifest format

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#64187: closed (guix locate: unsupported manifest format)
Date: Tue, 11 Jul 2023 16:23:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 11 Jul 2023 18:22:45 +0200
with message-id <87edle2zai.fsf <at> gnu.org>
and subject line Re: bug#64187: guix locate: unsupported manifest format
has caused the debbugs.gnu.org bug report #64187,
regarding guix locate: unsupported manifest format
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
64187: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64187
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ricardo Wurmus <rekado <at> elephly.net>
To: bug-guix <at> gnu.org
Subject: guix locate: unsupported manifest format
Date: Tue, 20 Jun 2023 09:25:09 +0200

I ran “guix locate” on the HPC cluster where we generally don’t ever run
“guix gc”.  Here’s what I got:

--8<---------------cut here---------------start------------->8---
$ time guix locate ls
guix locate: indexing files from /gnu/store...
guix locate: traversing local profile manifests...
guix locate: error: unsupported manifest format

real	2m24.029s
user	3m11.519s
sys	0m5.617s
--8<---------------cut here---------------end--------------->8---

It would be good if it printed the location of the problematic manifest
and ignored it.

-- 
Ricardo

[Message part 3 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: 64187-done <at> debbugs.gnu.org
Subject: Re: bug#64187: guix locate: unsupported manifest format
Date: Tue, 11 Jul 2023 18:22:45 +0200

Ludovic Courtès <ludo <at> gnu.org> skribis:

> Ricardo Wurmus <rekado <at> elephly.net> skribis:
>
>> Ludovic Courtès <ludo <at> 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…

Fixed in commit e1c2c2f042e8741c0759e21e634cd2271e078177!

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.