From: Marius Bakke <mbakke@fastmail.com>
To: Kei Kebreau <kei@openmailbox.org>, guix-devel@gnu.org
Subject: Re: [PATCH] gnu: maxima: Update to 5.39.0.
Date: Sun, 18 Dec 2016 16:41:26 +0100 [thread overview]
Message-ID: <87k2axnt21.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <871sx64614.fsf@openmailbox.org>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Kei Kebreau <kei@openmailbox.org> writes:
> This was supposed to be a simple version bump for Maxima, but it has
> come to my attention that Maxima hasn't built reproducibily for quite a
> while now (since version 5.36.1 according to my tests, possibly
> further). Is there any particular reason why? I can't seem to pinpoint
> the cause.
The patch looks good. Are you sure it was reproducible before?
I've found 'diffoscope' to be useful when troubleshooting
reproducibility problems. E.g. by running it on two cancelled builds, or
by installing to different output paths with a superficial change to the
expression. It will show sections that differs which may aid locating
the offending code.
For C family programs, a "hail mary" grep for __DATE__ or __TIME__ can
be enough. Tobias suggested making those return a fixed value, which I
think could be worthwhile, at least for the build environment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2016-12-18 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 21:09 [PATCH] gnu: maxima: Update to 5.39.0 Kei Kebreau
2016-12-18 15:41 ` Marius Bakke [this message]
2016-12-18 17:59 ` Kei Kebreau
2016-12-18 18:34 ` Marius Bakke
2016-12-18 19:10 ` Leo Famulari
2016-12-18 18:35 ` Leo Famulari
2016-12-19 4:50 ` Kei Kebreau
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=87k2axnt21.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=kei@openmailbox.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).