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: Mon, 8 Jun 2020 01:15:46 +0200 [thread overview]
Message-ID: <CAHecTjeZecr8HguqBnkLT=MQbmQJF3ea0FO1JRUWuHxO1d07tQ@mail.gmail.com> (raw)
In-Reply-To: <87wo4ir67g.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]
Actually, the biggest screenshot of the two was the end of the output of
the "guix pull" command after doing the "guix gc -D" command.
And the "build --repair" command resulted in this output:
guix build: error: error parsing derivation
`/gnu/store/8ablj2a1ihn32ilnfw1c3brpv9l7akzc-guile-json-4.0.1.drv':
expected string `Derive(['
So, that file was empty as
well: /gnu/store/8ablj2a1ihn32ilnfw1c3brpv9l7akzc-guile-json-4.0.1.drv
So I ran the "guix gc -D" on it, then "guix pull" again, and it found other
empty .drv's. I repeated this scheme until the "guix pull" command was
successful.
Thank you people so very much for your kind help!
My system is now bug free again. I don't know if I discovered real bugs, or
if my system crashing twice during a pull command somehow broke it, but I
hope this feedback helped. Maybe one day I will find out why my system
crashed and rebooted by itself a minute later. After all, it could have
been caused by something else on my system at that moment…
Have a good day! =)
On Sun, Jun 7, 2020 at 10:06 PM Ludovic Courtès <ludo@gnu.org> wrote:
> Hi Léon,
>
> Léon Lain Delysid <leon.lain.delysid@gmail.com> skribis:
>
> > 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.
>
> Did you try re-running ‘guix pull’ after the ‘guix gc -D’ command? (I
> don’t see it on the screenshot.)
>
> > But the corrupted filesystem idea might be that one. Can you give me
> > the best command to run a repair of the filesystem?
>
> If the suggestion above is not above, then you could try running this as
> root:
>
> guix build --repair \
>
> /gnu/store/m5djg8zwgl7nh0rm1av4nnlbwgwi0fwg-guix-daemon-1.1.0-4.bdc801e.drv
>
> Let me know how it goes.
>
> HTH,
> Ludo’.
>
[-- Attachment #2: Type: text/html, Size: 2440 bytes --]
next prev parent reply other threads:[~2020-06-07 23:17 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
2020-06-07 20:06 ` Ludovic Courtès
2020-06-07 23:15 ` Léon Lain Delysid [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHecTjeZecr8HguqBnkLT=MQbmQJF3ea0FO1JRUWuHxO1d07tQ@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.