From: Leo Famulari <leo@famulari.name>
To: Brett Gilio <brettg@posteo.net>
Cc: 34597@debbugs.gnu.org
Subject: bug#34597: `guix challenge` - 41 packages differ
Date: Wed, 20 Feb 2019 19:04:14 -0500 [thread overview]
Message-ID: <20190221000414.GC28504@jasmine.lan> (raw)
In-Reply-To: <87mumqhvcz.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
On Wed, Feb 20, 2019 at 05:51:24PM -0600, Brett Gilio wrote:
> Unless I am mistaken this isn't truly a reportable bug. As you can see
> in the guix challenge documentation
> https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-challenge.html
> the purpose of challenge is to check for deterministic qualities in
> reproducible packages. Right now, not all packages are reproducible as
> the guix team is hard at work trying to find the best solution for
> replacing binary seeds with something fully bootstrappable (see:
> https://bootstrappable.org)
There are a few types of reproducibility that we'd like to implement in
Guix. There is the bootstrapping issue, as you mentioned. But we can
still seek to build packages reproducibly even while Guix is built on
the binary seeds. In most cases that bootstrapping strategy does not
affect the reproducibility of packages.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-21 0:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 23:31 bug#34597: `guix challenge` - 41 packages differ mikadoZero
2019-02-20 23:51 ` Brett Gilio
2019-02-21 0:04 ` Leo Famulari [this message]
2019-02-21 0:48 ` mikadoZero
2019-02-21 15:51 ` Ricardo Wurmus
2019-02-21 0:01 ` Leo Famulari
2019-02-21 2:14 ` mikadoZero
2019-02-21 20:40 ` Leo Famulari
2019-02-22 16:59 ` mikadoZero
2019-02-22 18:35 ` Ricardo Wurmus
2019-03-04 22:05 ` bug#34597: Non-reproducible .go files 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=20190221000414.GC28504@jasmine.lan \
--to=leo@famulari.name \
--cc=34597@debbugs.gnu.org \
--cc=brettg@posteo.net \
/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.