unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Léon Lain Delysid" <leon.lain.delysid@gmail.com>
Cc: 41710@debbugs.gnu.org
Subject: bug#41710: Possibly found a bug while doing a "guix pull"
Date: Sun, 07 Jun 2020 22:06:43 +0200	[thread overview]
Message-ID: <87wo4ir67g.fsf@gnu.org> (raw)
In-Reply-To: <CAHecTjezH8uuU-+y7k_H+jSvf3oA3jr4u+AQCJ_oxSC7wTDF=A@mail.gmail.com> ("Léon Lain Delysid"'s message of "Sun, 7 Jun 2020 03:12:20 +0200")

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’.




  reply	other threads:[~2020-06-07 20:07 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 [this message]
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=87wo4ir67g.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41710@debbugs.gnu.org \
    --cc=leon.lain.delysid@gmail.com \
    /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).