From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: 27922@debbugs.gnu.org
Subject: [bug#27922] [PATCH] gnu: python-numpy: Update to 1.12.1.
Date: Tue, 26 Sep 2017 22:08:32 +0200 [thread overview]
Message-ID: <87efqtgr3z.fsf@gnu.org> (raw)
In-Reply-To: <20170926.185921.1683575194897240087.post@thomasdanckaert.be> (Thomas Danckaert's message of "Tue, 26 Sep 2017 18:59:21 +0200 (CEST)")
Hi,
Thomas Danckaert <post@thomasdanckaert.be> skribis:
> From: Leo Famulari <leo@famulari.name>
> Subject: Re: [bug#27922] [PATCH] gnu: python-numpy: Update to 1.12.1.
> Date: Tue, 26 Sep 2017 11:46:20 -0400
>
>> On Tue, Sep 26, 2017 at 01:48:45PM +0200, Ludovic Courtès wrote:
>>> Thomas Danckaert <post@thomasdanckaert.be> skribis:
>>> > I can push a modified patch (with the pypi source) if it's ok.
>>> Is there
>>> > any reason we would not update to version 1.13.1 rightaway?
>>>
>>> If the dependents of NumPy build fine, I see no reason not to
>>> upgrade to
>>> 1.13.1.
>>>
>>> Thanks for picking this up!
>>
>> Yes, thank you! I got distracted and had to take a little break,
>> which
>> is why this patch fell by the wayside.
>
> Attached patch updates to 1.13.1. I had to add bash-minimal as a
> native input because the numpy people made their build system a little
> more convoluted ;-) (external commands such as gcc are run within a
> shell with $SHELL -c 'gcc [...]', I didn't look up the motivation for
> that).
This is weird: bash-minimal is an implicit input already. What was the
error exactly?
Apart from that it looks great.
Thanks!
Ludo’.
next prev parent reply other threads:[~2017-09-26 20:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 19:49 [bug#27922] [PATCH] gnu: python-numpy: Update to 1.12.1 Leo Famulari
2017-08-02 20:12 ` Marius Bakke
2017-08-02 22:48 ` Leo Famulari
2017-09-04 13:19 ` Ludovic Courtès
2017-09-26 9:53 ` Thomas Danckaert
2017-09-26 11:48 ` Ludovic Courtès
2017-09-26 15:46 ` Leo Famulari
2017-09-26 16:59 ` Thomas Danckaert
2017-09-26 20:08 ` Ludovic Courtès [this message]
2017-09-27 6:36 ` Thomas Danckaert
2017-09-27 19:35 ` Ludovic Courtès
2017-09-28 18:32 ` Thomas Danckaert
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=87efqtgr3z.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27922@debbugs.gnu.org \
--cc=post@thomasdanckaert.be \
/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.