From: "Léon Lain Delysid" <leon.lain.delysid@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41710@debbugs.gnu.org
Subject: bug#41710: Possibly found a bug while doing a "guix pull"
Date: Sun, 7 Jun 2020 03:12:20 +0200 [thread overview]
Message-ID: <CAHecTjezH8uuU-+y7k_H+jSvf3oA3jr4u+AQCJ_oxSC7wTDF=A@mail.gmail.com> (raw)
In-Reply-To: <87a71guy5m.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1619 bytes --]
Hello, here's the result of the command you asked me to run. I executed it,
then did a "guix pull" again and got the same result. But the corrupted
filesystem idea might be that one. Can you give me the best command to run
a repair of the filesystem?
[image: Screenshot from 2020-06-07 03-05-33.jpg]
[image: Screenshot from 2020-06-07 02-50-54.jpg]
On Sat, Jun 6, 2020 at 3:22 PM Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> zimoun <zimon.toutoune@gmail.com> skribis:
>
> > ./guix/store.scm:1035:9: ERROR:
> > 1. &store-protocol-error:
> > message: "error parsing derivation
> >
> `/gnu/store/m5djg8zwgl7nh0rm1av4nnlbwgwi0fwg-guix-daemon-1.1.0-4.bdc801e.drv':
> > expected string `Derive(['"
> > status: 1
> > guix pull: error: You found a bug: the program
> > '/gnu/store/kpxami25fi3mrxb37sfbbx2s366chpk5-compute-guix-derivation'
> > failed to compute the derivation for Guix (version:
> > "415b90f24ee83059102f5fb0ce74a2bc0954fe58"; system: "x86_64-linux";
> > host version: "018cffc9c9e5a5855733f5f45a1c4d396bb6a321"; pull-version:
> 1).
> > Please report it by email to <bug-guix@gnu.org>.
>
> Léon, is this .drv file empty by any chance?
>
> If the answer is yes, that suggests a file system corruption. We see
> reports like this sometimes. It could maybe happen if the file system
> was not cleanly unmounted.
>
> The solution may be to run:
>
> guix gc -D
> /gnu/store/m5djg8zwgl7nh0rm1av4nnlbwgwi0fwg-guix-daemon-1.1.0-4.bdc801e.drv
>
> before re-running ‘guix pull’.
>
> Could you try that and report back?
>
> Thanks,
> Ludo’.
>
[-- Attachment #1.2: Type: text/html, Size: 2362 bytes --]
[-- Attachment #2: Screenshot from 2020-06-07 02-50-54.jpg --]
[-- Type: image/jpeg, Size: 566809 bytes --]
[-- Attachment #3: Screenshot from 2020-06-07 03-05-33.jpg --]
[-- Type: image/jpeg, Size: 942993 bytes --]
next prev parent reply other threads:[~2020-06-07 2:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 14:38 bug#41710: Possibly found a bug while doing a "guix pull" Léon Lain Delysid
2020-06-04 15:41 ` Julien Lepiller
2020-06-04 18:11 ` zimoun
2020-06-06 13:22 ` Ludovic Courtès
2020-06-07 1:12 ` Léon Lain Delysid [this message]
2020-06-07 20:06 ` Ludovic Courtès
2020-06-07 23:15 ` Léon Lain Delysid
2020-06-08 11:02 ` Danny Milosavljevic
2020-06-10 13:25 ` Ludovic Courtès
2020-06-12 9:55 ` Léon Lain Delysid
2020-06-07 1:19 ` Léon Lain Delysid
2020-06-07 1:15 ` Léon Lain Delysid
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='CAHecTjezH8uuU-+y7k_H+jSvf3oA3jr4u+AQCJ_oxSC7wTDF=A@mail.gmail.com' \
--to=leon.lain.delysid@gmail.com \
--cc=41710@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).