From: Thomas Danckaert <post@thomasdanckaert.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27922@debbugs.gnu.org
Subject: [bug#27922] [PATCH] gnu: python-numpy: Update to 1.12.1.
Date: Tue, 26 Sep 2017 11:53:55 +0200 [thread overview]
Message-ID: <cuca81h4wgc.fsf@thomasdanckaert.be> (raw)
In-Reply-To: <87vaky1u0m.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 04 Sep 2017 15:19:05 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Leo Famulari <leo@famulari.name> skribis:
>
>> On Wed, Aug 02, 2017 at 10:12:21PM +0200, Marius Bakke wrote:
>>> Leo Famulari <leo@famulari.name> writes:
>>>
>>> > * gnu/packages/python.scm (python-numpy, python2-numpy): Update to 1.12.1.
>>>
>>> LGTM ;-)
>>>
>>> > [source]: Download the "real" release tarball instead of the snapshot.
>>>
>>> NumPy provides a PGP signature with the zipball on PyPi:
>>>
>>> https://pypi.python.org/pypi/numpy
>>
>> Good catch!
>>
>>> Is there a reason to prefer the GitHub release tarball?
>>
>> Not that I know of. I only chose this tarball because I saw it on the GitHub
>> page. I'll try switching to PyPi.
>
> Leo, I think this fell through the cracks! :-)
>
> Ludo'.
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?
Thomas
next prev parent reply other threads:[~2017-09-26 9:55 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 [this message]
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
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
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=cuca81h4wgc.fsf@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=27922@debbugs.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 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).