From: Brice Waegeneire <brice@waegenei.re>
To: Lo Peter <peterloleungyau@gmail.com>
Cc: Help-Guix <help-guix-bounces+brice+lists=waegenei.re@gnu.org>,
help-guix <help-guix@gnu.org>
Subject: Re: How to debug / investigate non-reproducible build for r-repr?
Date: Mon, 29 Jun 2020 09:13:20 +0000 [thread overview]
Message-ID: <69720a2c9c1f94cdf5e576ac81f12053@waegenei.re> (raw)
In-Reply-To: <CAEM+zmin=q2z+zhiOR0kkZ0mi8F--a2oKyYm3EM=2AxL4rYpKA@mail.gmail.com>
Hello Peter,
On 2020-06-29 08:25, Lo Peter wrote:
> I am trying to import r-languageserver, and one of its dependency is
> r-repr, which I found that cannot be built reproducibly (on my
> laptop's guix, installed on Linux Mint), i.e.
>
> guix build --rounds=2 r-repr
>
> would give the error saying that "...r-repr-1.1.0.drv differs from
> previous round".
>
> How should I begin to investigate the issue?
I'm new to fixing non reproductible build, all I ever needed thus
far is using 'diffoscope'. Note that this program has a lot of
optional dependencies that aren't installed by default but you
get a warning when 'diffoscope' can make uses of such dependencies,
in the case of 'r-repr' it wants to use 'Rscript'.
Here is quick use of it:
--8<---------------cut here---------------start------------->8---
$ guix environment --ad-hoc diffoscope r
$ guix build r-repr --check --keep-failed
…
guix build: error: derivation
`/gnu/store/5rbf3kb0s96m1nij5s631j1k3mnh75lg-r-repr-1.1.0.drv' may not
be deterministic: output
`/gnu/store/aah5bpxg1h3sf09ca1plp4cbj745n95y-r-repr-1.1.0' differs from
‘/gnu/store/aah5bpxg1h3sf09ca1plp4cbj745n95y-r-repr-1.1.0-check’
$ diffoscope --exclude-command stat
/gnu/store/aah5bpxg1h3sf09ca1plp4cbj745n95y-r-repr-1.1.0{,-check}
--8<---------------cut here---------------end--------------->8---
- Brice
next prev parent reply other threads:[~2020-06-29 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 8:25 How to debug / investigate non-reproducible build for r-repr? Lo Peter
2020-06-29 9:13 ` Brice Waegeneire [this message]
2020-06-29 10:19 ` zimoun
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=69720a2c9c1f94cdf5e576ac81f12053@waegenei.re \
--to=brice@waegenei.re \
--cc=help-guix-bounces+brice+lists=waegenei.re@gnu.org \
--cc=help-guix@gnu.org \
--cc=peterloleungyau@gmail.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.
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).