From: Danny Milosavljevic <dannym@scratchpost.org>
To: Ethan O'Quin <ethan.a.oquin@protonmail.com>
Cc: 33862@debbugs.gnu.org
Subject: bug#33862: "guix gc" failing to complete
Date: Tue, 25 Dec 2018 08:51:05 +0100 [thread overview]
Message-ID: <20181225085105.6c1c36b9@scratchpost.org> (raw)
In-Reply-To: <GA8iS1aNem02oYkFHr8_hBiLm8tRWKPIlQOgnexihwSTg-QQ_dnKrQkKEBhsi3iFL7cEn0mGXkLIjzXHSv5EKT8F4CNtLndnoMN4kS0q2es=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
Hi,
On Mon, 24 Dec 2018 22:33:47 +0000
Ethan O'Quin <ethan.a.oquin@protonmail.com> wrote:
> Every time I run "guix gc" the process fails with:
>
> "guix gc: error: build failed: executing SQLite statement: FOREIGN KEY constraint failed"
>
> This occurs every time "guix gc" is run, although it progresses for a moment before it fails.
>
> The issue was encountered on guix 0.16.0-7.6f1e0bb on GuixSD as of December 24, although I have encountered it repeatedly back to some time in October, possibly earlier.
Try
# guix gc --verify
If that doesn't work, then
$ cp /var/guix/db/db.sqlite /tmp/
$ sqlite3 /tmp/db.sqlite
sqlite> .tables
sqlite> .schema Refs
Do you see a foreign key here with "on delete restrict", Refs.reference ?
sqlite> .schema DerivationOutputs
No "on delete restrict" here?
sqlite> .schema FailedPaths
No "on delete restrict" here?
sqlite> .schema ValidPaths
No "on delete restrict" here?
Also, is there a hash value somewhere in the error messages?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-25 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 22:33 bug#33862: "guix gc" failing to complete Ethan O'Quin
2018-12-25 7:51 ` Danny Milosavljevic [this message]
2019-04-06 10:44 ` pkill9
2020-12-19 0:09 ` zimoun
2021-01-11 15:27 ` zimoun
2021-02-09 17:59 ` zimoun
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=20181225085105.6c1c36b9@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=33862@debbugs.gnu.org \
--cc=ethan.a.oquin@protonmail.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 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.