all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Update Julia to 0.4.2.
Date: Mon, 4 Jan 2016 12:54:35 +0100	[thread overview]
Message-ID: <idj37udimpw.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87poxoszd0.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>
>> Unfortunately, the build for “julia” is not reproducible.  I haven’t yet
>> investigated what might be the cause and I don’t know yet how large the
>> difference between two builds is.
>
> Julia is not mentioned in packages.yml in
> <git://git.debian.org/git/reproducible/notes.git>, so I guess nobody has
> looked at it yet.
>
> When you have diff or Diffoscope info about the differences, please open
> a bug.

There are some obvious things (such as embedding a timestamp in a
version string).  Maybe changing those things would be sufficient
already.  I’ll play with this first.  If I cannot find anything else
I’ll report a bug as soon as I have something to share.

>> From 034cdddd452c036d5155a56da35d20e97d0e9f28 Mon Sep 17 00:00:00 2001
>> From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
>> Date: Mon, 30 Nov 2015 14:22:18 +0100
>> Subject: [PATCH 2/3] gnu: Add libuv-julia.
>>
>> * gnu/packages/julia.scm (libuv-julia): New variable.
>
> [...]
>
>> +(define-public libuv-julia
>
> Perhaps this can be kept private?  If not, I would suggest changing the
> ‘synopsis’ field as well.

I made it private.

> Thanks, and sorry for the delay!

No problem.  (There’s no urgency.) Thanks for the review!

~~ Ricardo

      reply	other threads:[~2016-01-04 11:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 11:56 [PATCH] Update Julia to 0.4.2 Ricardo Wurmus
2015-12-30 15:57 ` Ludovic Courtès
2016-01-04 11:54   ` Ricardo Wurmus [this message]

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=idj37udimpw.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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 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.