From: Marius Bakke <mbakke@fastmail.com>
To: 30875@debbugs.gnu.org
Subject: bug#30875: Garbage collector may leave empty files
Date: Tue, 20 Mar 2018 12:21:36 +0100 [thread overview]
Message-ID: <87muz3f0vz.fsf@fastmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
Hello,
Recently I've seen a couple of instances like these:
exporting path `/gnu/store/mi1rbw8fdsbi4bc4pndbb6smq39722vm-baobab-3.26.1.tar.xz'
guix offload: error: build failed: hash of path `/gnu/store/mi1rbw8fdsbi4bc4pndbb6smq39722vm-baobab-3.26.1.tar.xz' has changed from `4223b4813b2253e68ea2b824d0d0e284ff75714ad0faf5a33d65a78df6b65915' to `77ac62e2629d8e45f624589c0c8bf99e24b3a722349bf1e79bc186008534e246'!
cannot build derivation `/gnu/store/jbx6a4n1d55dpydr87d11m7xwapm3pcx-gnome-3.24.3.drv': 1 dependencies couldn't be built
Without the build hook, it manifests as:
starting phase `unpack'
tar: This does not look like a tar archive
xz: (stdin): File format not recognized
tar: Child returned status 1
tar: Error is not recoverable: exiting now
There was another instance on help-guix recently with a user having
empty .drv files in the store.
There is a bug lurking here somewhere, but I'm not sure where to start
looking.
$ find /gnu/store/ -maxdepth 1 -size 0 | grep -v '\.lock$' | wc -l
24
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2018-03-20 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 11:21 Marius Bakke [this message]
2018-03-20 23:09 ` bug#30875: Garbage collector may leave empty files Ludovic Courtès
2018-03-21 0:20 ` Mark H Weaver
2018-03-21 20:33 ` Ludovic Courtès
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=87muz3f0vz.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=30875@debbugs.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 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).