From: ludo@gnu.org (Ludovic Courtès)
To: guix-sysadmin@gnu.org
Cc: 25016@debbugs.gnu.org
Subject: bug#25016: Old build daemons lead to non-reproducible builds
Date: Thu, 24 Nov 2016 14:09:50 +0100 [thread overview]
Message-ID: <87d1hl6n35.fsf@gnu.org> (raw)
Hi!
Old versions of guix-daemon would use /tmp/nix-build-… as the build
directory name instead of /tmp/guix-build-… (commit
7a57c96a1024e6b74359ba561110f19f92b89b06), and versions prior to 0.11.0
could use a different directory prefix (.drv-0, .drv-1, etc.) whereas
current versions systematically use .drv-0 (commit
cb9601029ea164b86bdf997f7160d494c15d344b).
However, some of our build machines run old daemons, which leads to
discrepancies such has:
--8<---------------cut here---------------start------------->8---
$ wget -O - https://mirror.hydra.gnu.org/nar/3kxg1wvc1dnw9bdnp61pfc6vy14v4ikl-bash-4.4.0-include |bunzip2 |guix archive -x /tmp/foo
[…]
$ diff -ruBb /gnu/store/3kxg1wvc1dnw9bdnp61pfc6vy14v4ikl-bash-4.4.0-include /tmp/foo
diff -ruBb /gnu/store/3kxg1wvc1dnw9bdnp61pfc6vy14v4ikl-bash-4.4.0-include/lib/bash/Makefile.inc /tmp/foo/lib/bash/Makefile.inc
--- /gnu/store/3kxg1wvc1dnw9bdnp61pfc6vy14v4ikl-bash-4.4.0-include/lib/bash/Makefile.inc 1970-01-01 01:00:01.000000000 +0100
+++ /tmp/foo/lib/bash/Makefile.inc 2016-11-24 14:00:26.449665970 +0100
@@ -38,7 +38,7 @@
headersdir = $(includedir)/$(PACKAGE_NAME)
topdir = ../..
-BUILD_DIR = /tmp/guix-build-bash-4.4.0.drv-0/bash-4.4
+BUILD_DIR = /tmp/nix-build-bash-4.4.0.drv-0/bash-4.4
srcdir = .
--8<---------------cut here---------------end--------------->8---
This can lead to hash mismatches between what the narinfo claims and
what the nar actually contains (due to caching), which annoys users.
We should update all our build machines to a newer daemon.
Ludo’.
next reply other threads:[~2016-11-24 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 13:09 Ludovic Courtès [this message]
2016-12-02 23:07 ` bug#25016: Old build daemons lead to non-reproducible builds Ludovic Courtès
2017-05-04 21:51 ` Ludovic Courtès
2017-05-05 6:53 ` Ricardo Wurmus
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=87d1hl6n35.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25016@debbugs.gnu.org \
--cc=guix-sysadmin@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).