From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: python3-{jaraco*,portend,tempora}: update and switch to python-pep517
Date: Sun, 22 May 2022 13:36:10 +0200 [thread overview]
Message-ID: <20220522113610.Ibr5eGljy_OjnlM7lBOPPKynMP0DAwv-SpAzk32Is0c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36303@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
There's a merged pull request on the void-packages repository
python3-{jaraco*,portend,tempora}: update and switch to python-pep517
https://github.com/void-linux/void-packages/pull/36303
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
Needs to be tested with:
- [x] python3-CherryPy (depends on python3-portend and python3-jaraco.collections)
- [x] python3-Cheroot (depends on python3-jaraco.functools)
- [x] sabnzbd (depends on python3-portend)
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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:[~2022-05-22 11:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 19:57 [PR PATCH] python3-{jaraco*,portend,tempora} " tibequadorian
2022-03-23 20:19 ` [PR PATCH] [Updated] python3-{jaraco*,portend,tempora}: " tibequadorian
2022-03-23 21:00 ` tibequadorian
2022-03-23 21:08 ` tibequadorian
2022-03-23 21:31 ` tibequadorian
2022-03-23 21:32 ` tibequadorian
2022-03-24 11:29 ` tibequadorian
2022-03-24 11:44 ` tibequadorian
2022-05-03 13:29 ` ahesford
2022-05-04 11:52 ` [PR PATCH] [Updated] " tibequadorian
2022-05-22 11:36 ` 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=20220522113610.Ibr5eGljy_OjnlM7lBOPPKynMP0DAwv-SpAzk32Is0c@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).