From: Brett Gilio <brettg@posteo.net>
To: mikadoZero <mikadozero@yandex.com>
Cc: 34597@debbugs.gnu.org
Subject: bug#34597: `guix challenge` - 41 packages differ
Date: Wed, 20 Feb 2019 17:51:24 -0600 [thread overview]
Message-ID: <87mumqhvcz.fsf@posteo.net> (raw)
In-Reply-To: <20190220233151.GA23130@z.z>
mikadoZero writes:
> After running `guix challenge` there are some packages which differ from ones I have built locally.
Hi Mikado,
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)
If you look, all of the packages you showed are related to the guix core
system, which means that you are not getting any non-deterministic
packages from the relevant /gnu package repositories, which is good.
I think this bug can probably be closed.
All the best,
Brett Gilio
next prev parent reply other threads:[~2019-02-20 23:52 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 [this message]
2019-02-21 0:04 ` Leo Famulari
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=87mumqhvcz.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=34597@debbugs.gnu.org \
--cc=mikadozero@yandex.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.