From: ludo@gnu.org (Ludovic Courtès)
To: carl hansen <carlhansen1234@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: damaged installation
Date: Tue, 02 Oct 2018 12:04:23 +0200 [thread overview]
Message-ID: <87y3bgpsuw.fsf@gnu.org> (raw)
In-Reply-To: <CAHEkXCQb-h014YgccZLvrt4db8v=Te4Bi5CE5juH_Z2UnyudxQ@mail.gmail.com> (carl hansen's message of "Fri, 28 Sep 2018 01:25:43 -0700")
Hello,
carl hansen <carlhansen1234@gmail.com> skribis:
> On Thu, Sep 27, 2018 at 12:48 AM Mark H Weaver <mhw@netris.org> wrote:
>>
>> carl hansen <carlhansen1234@gmail.com> writes:
>>
>> > I installed guix 0.15 on Debian testing system
>> > Power went out while 'guix pull'ing or something.
>> > Now, show stopper error. Attached. How to proceed?
>>
>> I would move .config/guix to another location (or simply delete it),
>> optionally run "guix gc --verify=contents", and then rerun "guix pull".
>>
>> Mark
>
> I tried suggestions, no good. I reinstalled from the beginning ,
> starting with the guix.binary0.15.x86_64.tar.gz
> TWICE and I get same problem:
If you unpacked the guix-binary tarball on top of your system, it’s
likely that the store is now corrupt.
You should at least “rm -rf /gnu /var/guix /etc/guix ~/.config/guix”
before unpacking the tarball. (Though you shouldn’t need to reinstall
from the tarball in the first place.)
HTH!
Ludo’.
prev parent reply other threads:[~2018-10-02 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 7:23 damaged installation carl hansen
2018-09-26 18:36 ` znavko
2018-09-27 7:23 ` Ricardo Wurmus
2018-09-27 7:48 ` Mark H Weaver
2018-09-28 8:25 ` carl hansen
2018-10-02 10:04 ` Ludovic Courtès [this message]
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=87y3bgpsuw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=carlhansen1234@gmail.com \
--cc=help-guix@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.
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).