unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: maxima: Update to 5.39.0.
Date: Sun, 18 Dec 2016 14:10:01 -0500	[thread overview]
Message-ID: <20161218191001.GA16797@jasmine> (raw)
In-Reply-To: <87h961nl1j.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>

[-- Attachment #1: Type: text/plain, Size: 913 bytes --]

On Sun, Dec 18, 2016 at 07:34:32PM +0100, Marius Bakke wrote:
> Kei Kebreau <kei@openmailbox.org> writes:
> 
> >> 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.
> >>
> >
> > Yes. I see that diffoscope complains about missing 'xxd'. That may be
> > useful to package (unless we already have it and I'm just oblivious).
> 
> 'xxd' is distributed with the 'vim' package. Is the error fatal? Perhaps
> we should patch diffoscope with the absolute path to xxd.

The warning message in the source code is:

"xxd not available in path. Falling back to Python hexlify."

So, I guess the built-in hexlify is a fine fall-back for now.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2016-12-18 19:10 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
2016-12-18 17:59   ` Kei Kebreau
2016-12-18 18:34     ` Marius Bakke
2016-12-18 19:10       ` Leo Famulari [this message]
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=20161218191001.GA16797@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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 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).