From: Leo Famulari <leo@famulari.name>
To: mikadoZero <mikadozero@yandex.com>
Cc: 34597@debbugs.gnu.org
Subject: bug#34597: `guix challenge` - 41 packages differ
Date: Wed, 20 Feb 2019 19:01:34 -0500 [thread overview]
Message-ID: <20190221000134.GB28504@jasmine.lan> (raw)
In-Reply-To: <20190220233151.GA23130@z.z>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On Wed, Feb 20, 2019 at 06:31:51PM -0500, mikadoZero wrote:
> After running `guix challenge` there are some packages which differ from ones I have built locally.
Thanks!
> `guix --version`:
> guix (GNU Guix) 34372d3905e17c880180f811e5b5f83e423e9025
There is also `guix describe` which allows others to completely
reproduce your environment.
> /gnu/store/0yzw2jrpzf0f4gg2i3dqy80ddkgrgf5c-guix-cli contents differ:
> local hash: 0jamz4xnkh3rf10fz6f5dcs046h4jxiyqg7byrqbj2wqk7lq1mdl
> https://ci.guix.info/nar/gzip/0yzw2jrpzf0f4gg2i3dqy80ddkgrgf5c-guix-cli: 00rdkjc12xrd3jj41k32gcizd0kfz47f9g8pkixrp04mi5vxnp5n
[...]
So these are all parts of Guix itself. Can you compare a couple of these
non-reproducible pairs of files and reply with the differences here?
Some useful tools available from Guix are diffoscope and vbindiff.
Since they are all part of Guix and using Guile I think the issue will
be the same for all of them.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-21 0:02 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
2019-02-21 0:48 ` mikadoZero
2019-02-21 15:51 ` Ricardo Wurmus
2019-02-21 0:01 ` Leo Famulari [this message]
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=20190221000134.GB28504@jasmine.lan \
--to=leo@famulari.name \
--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.