From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-h2: update to 4.1.0.
Date: Fri, 31 Dec 2021 00:21:26 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34769@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
There is a new pull request by unspecd against master on the void-packages repository
https://github.com/unspecd/void-packages pkg/python3-h2
https://github.com/void-linux/void-packages/pull/34769
python3-h2: update to 4.1.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### 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
-->
A patch file from https://github.com/void-linux/void-packages/pull/34769.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pkg/python3-h2-34769.patch --]
[-- Type: text/x-diff, Size: 1279 bytes --]
From 087fd56735fff383f40dd4c26cd6f965a7795063 Mon Sep 17 00:00:00 2001
From: Evgeny Ermakov <evgeny.v.ermakov@gmail.com>
Date: Fri, 31 Dec 2021 10:18:21 +1100
Subject: [PATCH] python3-h2: update to 4.1.0.
---
srcpkgs/python3-h2/template | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-h2/template b/srcpkgs/python3-h2/template
index 29668e4cec4f..24cd2b540bd8 100644
--- a/srcpkgs/python3-h2/template
+++ b/srcpkgs/python3-h2/template
@@ -1,17 +1,18 @@
# Template file for 'python3-h2'
pkgname=python3-h2
-version=4.0.0
-revision=2
+version=4.1.0
+revision=1
wrksrc="h2-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools"
-depends="python3 python3-hpack python3-hyperframe"
+depends="python3-hpack python3-hyperframe"
+checkdepends="${depends} python3-hypothesis python3-pytest"
short_desc="HTTP/2 State-Machine based protocol implementation (Python3)"
maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://github.com/python-hyper/h2"
distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=78753b52cebb63f87097c9a5f969004a61ec4a41f967e41dcc287e26dd9b4143
+checksum=4a17b1ec23152bd94ab6260ea61f6cc02de92bd7c36762f13e34fdecea454b41
post_install() {
vlicense LICENSE
next reply other threads:[~2021-12-30 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 23:21 unspecd [this message]
2022-01-01 21:14 ` [PR PATCH] [Closed]: " unspecd
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-34769@inbox.vuxu.org \
--to=unspecd@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).