From: joelchrono12 <joelchrono12@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: python3-aiostream-0.4.5
Date: Mon, 09 Jan 2023 03:35:49 +0100 [thread overview]
Message-ID: <20230109023549.PDLWaPi_foxVov4CFb6LEFVaWgPyVUV_Wunpt-QtqyY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41530@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
There is an updated pull request by joelchrono12 against master on the void-packages repository
https://github.com/joelchrono12/void-packages python3-aiostream
https://github.com/void-linux/void-packages/pull/41530
New package: python3-aiostream-0.4.5
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
A patch file from https://github.com/void-linux/void-packages/pull/41530.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-aiostream-41530.patch --]
[-- Type: text/x-diff, Size: 1121 bytes --]
From 2b42b4692bb7cc3a7dfe4e73fa56e39b6801219c Mon Sep 17 00:00:00 2001
From: joelchrono12 <joel.chrono@disroot.org>
Date: Sun, 8 Jan 2023 20:31:05 -0600
Subject: [PATCH] New package: python3-aiostream-0.4.5
---
srcpkgs/python3-aiostream/template | 14 ++++++++++++++
1 file changed, 14 insertions(+)
create mode 100644 srcpkgs/python3-aiostream/template
diff --git a/srcpkgs/python3-aiostream/template b/srcpkgs/python3-aiostream/template
new file mode 100644
index 000000000000..ac660ea98eac
--- /dev/null
+++ b/srcpkgs/python3-aiostream/template
@@ -0,0 +1,14 @@
+# Template file for 'python3-aiostream'
+pkgname=python3-aiostream
+version=0.4.5
+revision=1
+build_style=python3-module
+hostmakedepends="python3-setuptools"
+depends="python3"
+short_desc="Generator-based operators for asynchronous iteration"
+maintainer="joelchrono12 <joel.chrono@disroot.org>"
+license="GPL-3.0"
+homepage="https://aiostream.readthedocs.io/"
+distfiles="${PYPI_SITE}/a/aiostream/aiostream-${version}.tar.gz"
+checksum=3ecbf87085230fbcd9605c32ca20c4fb41af02c71d076eab246ea22e35947d88
+homepage="https://aiostream.readthedocs.io/"
next prev parent reply other threads:[~2023-01-09 2:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 2:34 [PR PATCH] " joelchrono12
2023-01-09 2:35 ` joelchrono12 [this message]
2023-01-09 14:10 ` [PR PATCH] [Updated] " joelchrono12
2023-01-10 22:36 ` Piraty
2023-01-10 23:36 ` joelchrono12
2023-01-10 23:36 ` joelchrono12
2023-01-11 1:12 ` classabbyamp
2023-01-14 3:30 ` [PR PATCH] [Updated] " joelchrono12
2023-01-14 3:37 ` joelchrono12
2023-01-14 3:39 ` vdirsyncer: update to 0.19.0 joelchrono12
2023-01-15 4:26 ` [PR PATCH] [Updated] " joelchrono12
2023-01-15 9:12 ` [PR REVIEW] " paper42
2023-01-15 9:12 ` paper42
2023-01-15 9:12 ` paper42
2023-01-20 17:29 ` ahesford
2023-01-20 17:29 ` [PR PATCH] [Closed]: " ahesford
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=20230109023549.PDLWaPi_foxVov4CFb6LEFVaWgPyVUV_Wunpt-QtqyY@z \
--to=joelchrono12@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).