From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gerwitz <mtg@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Recovering from broken Guix due to GC'd derivations
Date: Mon, 11 Jun 2018 13:08:52 +0200 [thread overview]
Message-ID: <87d0wxlgvv.fsf@gnu.org> (raw)
In-Reply-To: <87d0wye257.fsf@gnu.org> (Mike Gerwitz's message of "Sun, 10 Jun 2018 17:56:52 -0400")
Hi Mike,
Mike Gerwitz <mtg@gnu.org> skribis:
> On Sun, Jun 10, 2018 at 18:45:19 +0200, Ludovic Courtès wrote:
>> Hello Mike,
>>
>> Mike Gerwitz <mtg@gnu.org> skribis:
>>
>>> Any pull or package install operations that I attempt give me an error
>>> like this (the exact derivation varies between my user and root, but
>>> they're both Perl):
>>>
>>> guix pull: error: open-file: No such file or directory:
>>> "/gnu/store/fq9583a3w3is0r1yrjxg1znfz2qkvg78-perl-5.26.2.tar.xz.drv"
>>
>> This cannot happen under normal circumstances, as we say. Could it be
>> that you run a Guix configured with a different ‘localstatedir’ than the
>> original one that populated /gnu/store?
>
> I've never done anything other than a normal `guix pull`. When I was
> working on the `guix environment` changes for containers months ago, I
> was using `pre-inst-env', but nothing other than that. I didn't provide
> any options to `configure' or anything change any other env vars.
>
> Since before March, I've just been using a vanilla guix (rather than my
> local git checkout).
Hmm weird. Did you try running ‘guix gc --verify’? I don’t see how one
could end up in such a state, unless there’s some hard disk corruption
or something.
Ludo’.
next prev parent reply other threads:[~2018-06-11 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 2:01 Recovering from broken Guix due to GC'd derivations Mike Gerwitz
2018-06-10 10:52 ` Jone
2018-06-10 16:45 ` Ludovic Courtès
2018-06-10 21:56 ` Mike Gerwitz
2018-06-11 11:08 ` Ludovic Courtès [this message]
2018-06-12 2:31 ` Mike Gerwitz
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=87d0wxlgvv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=mtg@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.