From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Stuck with corrupt store
Date: Sun, 12 Jun 2016 18:19:53 +0200 [thread overview]
Message-ID: <87eg82mlau.fsf@gnu.org> (raw)
In-Reply-To: <575D4A4D.2050005@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 12 Jun 2016 13:41:01 +0200")
Hi!
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> I deleted /gnu/store/*-nose-* (can't remember why).
You deleted with “rm -rf”?
In that case, even though ‘guix gc --verify=repair’ should be able to
help, remember that this voids your warranty. :-)
> Further when I run guix gc, I get an "FOREIGN KEY constraint failed"
> error, which `--verify=repair` is not able to repair.
Someone already reported it, so there may be a bug here. I’ll see if we
can reproduce it.
Ludo’.
next prev parent reply other threads:[~2016-06-12 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 11:41 Stuck with corrupt store Hartmut Goebel
2016-06-12 16:19 ` Ludovic Courtès [this message]
2016-06-12 16:26 ` Hartmut Goebel
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=87eg82mlau.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=h.goebel@crazy-compilers.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).