all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Reproducible installation images
Date: Mon, 11 Dec 2017 14:21:00 +0100	[thread overview]
Message-ID: <87vahd1jur.fsf@gnu.org> (raw)
In-Reply-To: <20171211093649.rbka5xk6ojrcvhtf@abyayala> (ng0@n0.is's message of "Mon, 11 Dec 2017 09:36:49 +0000")

ng0 <ng0@n0.is> skribis:

> Ludovic Courtès transcribed 2.6K bytes:

[...]

>> However, disk images are likely not bit-reproducible currently,
>> primarily due to non-determinism in how file systems populate the disk.
>> 
>> They might be reproducible if ‘guix system’ always creates files in the
>> same order, which is something we could enforce (perhaps that’s already
>> the case).  If it’s not sufficient, then we should look at what others
>> in the reproducible-builds.org effort have been doing (Tails achieved
>> reproducible ISO images, for instance, and I think OpenWrt people were
>> looking at ext2 reproducibility.)
>> 
>> There may also be lingering non-reproducibility issues in some of the
>> packages included that need to be addressed.
>> 
>> It would be good to investigate!
>
> Definitely, I agree. Should we open a new bug ticket to track this effort?

Sure, two even: one for the binary tarball, one for the GuixSD ISO
image.

Ludo’.

  reply	other threads:[~2017-12-11 13:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 12:45 GNU Guix & GuixSD 0.14.0 released Ludovic Courtès
2017-12-07 17:05 ` Konrad Hinsen
2017-12-08 22:41 ` Mark H Weaver
2017-12-11  9:30   ` Reproducible installation images Ludovic Courtès
2017-12-11  9:36     ` ng0
2017-12-11 13:21       ` Ludovic Courtès [this message]
2017-12-12  0:12     ` Mark H Weaver
2017-12-12  9:27       ` Ludovic Courtès
2017-12-12 22:25         ` Mark H Weaver
2017-12-15 14:37           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vahd1jur.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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 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.