Github messages for voidlinux
 help / color / mirror / Atom feed
From: bra1nwave <bra1nwave@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-numpy: update to 1.18.3.
Date: Sat, 25 Apr 2020 19:37:45 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21334@inbox.vuxu.org> (raw)

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

There is a new pull request by bra1nwave against master on the void-packages repository

https://github.com/bra1nwave/void-packages numpy
https://github.com/void-linux/void-packages/pull/21334

python3-numpy: update to 1.18.3.


A patch file from https://github.com/void-linux/void-packages/pull/21334.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-numpy-21334.patch --]
[-- Type: text/x-diff, Size: 1209 bytes --]

From acfab808151d2a555cb58e08f410eddc1d2c811a Mon Sep 17 00:00:00 2001
From: bra1nwave <bra1nwave@protonmail.com>
Date: Sat, 25 Apr 2020 19:36:58 +0200
Subject: [PATCH] python3-numpy: update to 1.18.3.

---
 srcpkgs/python3-numpy/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/python3-numpy/template b/srcpkgs/python3-numpy/template
index cffe4080bf7..e230c7ee12d 100644
--- a/srcpkgs/python3-numpy/template
+++ b/srcpkgs/python3-numpy/template
@@ -1,7 +1,7 @@
 # Template file for 'python3-numpy'
 pkgname=python3-numpy
-version=1.18.2
-revision=2
+version=1.18.3
+revision=1
 wrksrc="numpy-${version}"
 build_style=python3-module
 hostmakedepends="python3-setuptools python3-Cython gcc-fortran"
@@ -13,11 +13,11 @@ maintainer="bra1nwave <bra1nwave@protonmail.com>"
 license="BSD-3-Clause"
 homepage="https://www.numpy.org/"
 distfiles="https://github.com/numpy/numpy/archive/v${version}.tar.gz"
-checksum=fdf3ed4e260e1af08b6743527634e85f999caba60d2525c1d6f5aea79f5a6d1f
+checksum=a44fe209fdfe7fd59d76e6297637367b57f3d9bd3b2b10ea7efc0028818db2de
 alternatives="numpy:f2py:/usr/bin/f2py3"
 
 do_check() {
-	./runtests.py
+	./runtests.py -v
 }
 
 post_install() {

             reply	other threads:[~2020-04-25 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-25 17:37 bra1nwave [this message]
2020-04-25 19:54 ` [PR PATCH] [Merged]: " Hoshpak

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21334@inbox.vuxu.org \
    --to=bra1nwave@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).