From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: python3-numpy-stl: update to 2.15.1.
Date: Wed, 24 Feb 2021 17:14:41 +0100 [thread overview]
Message-ID: <20210224161441.42LTPcgrNztrdVJaRMwTZJ56A4PUXzrrew_Vc6EwiMM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28677@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
There's a merged pull request on the void-packages repository
python3-numpy-stl: update to 2.15.1.
https://github.com/void-linux/void-packages/pull/28677
Description:
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [X] I generally don't use the affected packages but briefly tested this PR
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [X] I built this PR locally for my native architecture, (x64-glibc)
- [X] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [X] aarch64-musl
- [X] armv7l
- [X] armv6l-musl
~~Note: check fails because one of the test files has incorrect line endings. I've opened a pr with upstream.~~
Fixed
prev parent reply other threads:[~2021-02-24 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 20:39 [PR PATCH] " karl-nilsson
2021-02-20 21:45 ` [PR PATCH] [Updated] " karl-nilsson
2021-02-20 21:58 ` karl-nilsson
2021-02-24 16:14 ` 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=20210224161441.42LTPcgrNztrdVJaRMwTZJ56A4PUXzrrew_Vc6EwiMM@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).