From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: python3-numpy: update to 1.25.0.
Date: Mon, 26 Jun 2023 18:04:38 +0200 [thread overview]
Message-ID: <20230626160438.VIk80AvLUE174Sr1IS5ItvsSFTdvyKytuhH-BxyOE84@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44529@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
There's a merged pull request on the void-packages repository
python3-numpy: update to 1.25.0.
https://github.com/void-linux/void-packages/pull/44529
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
I enabled check, and I'm currently testing with sagemath to see what fails and fix it. So far I've only tried x86_64.
I didn't change the build-style to pep517 because that won't allow parallel build. For testing, a custom `do_check()` is needed in any case. Moreover, it seems numpy will soon move to meson for building so we may as well wait for that.
@ahesford
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2023-06-26 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 2:34 [PR PATCH] " tornaria
2023-06-20 2:39 ` [PR REVIEW] " ahesford
2023-06-20 2:40 ` tornaria
2023-06-20 3:02 ` tornaria
2023-06-20 20:46 ` tornaria
2023-06-20 21:18 ` tornaria
2023-06-20 21:24 ` tornaria
2023-06-21 2:46 ` ahesford
2023-06-22 21:13 ` [PR PATCH] [Updated] " tornaria
2023-06-22 21:22 ` tornaria
2023-06-25 0:04 ` tornaria
2023-06-26 2:47 ` [PR PATCH] [Updated] " tornaria
2023-06-26 3:19 ` tornaria
2023-06-26 16:04 ` ahesford [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=20230626160438.VIk80AvLUE174Sr1IS5ItvsSFTdvyKytuhH-BxyOE84@z \
--to=ahesford@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).