From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-tenacity: update to 8.1.0.
Date: Wed, 21 Sep 2022 19:52:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39404@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
There is a new pull request by jcgruenhage against master on the void-packages repository
https://github.com/jcgruenhage/void-packages python3-tenacity-8.0.1_1
https://github.com/void-linux/void-packages/pull/39404
python3-tenacity: update to 8.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 [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
-->
A patch file from https://github.com/void-linux/void-packages/pull/39404.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-tenacity-8.0.1_1-39404.patch --]
[-- Type: text/x-diff, Size: 1104 bytes --]
From 47ce2386d4e382f5aea19e7d0b374b994c9d6f91 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
<jan.christian@gruenhage.xyz>
Date: Wed, 21 Sep 2022 19:50:47 +0200
Subject: [PATCH] python3-tenacity: update to 8.1.0.
---
srcpkgs/python3-tenacity/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-tenacity/template b/srcpkgs/python3-tenacity/template
index 1182563e46e2..cb4257c28d84 100644
--- a/srcpkgs/python3-tenacity/template
+++ b/srcpkgs/python3-tenacity/template
@@ -1,6 +1,6 @@
# Template file for 'python3-tenacity'
pkgname=python3-tenacity
-version=8.0.1
+version=8.1.0
revision=1
wrksrc="${pkgname/python3-/}-${version}"
build_style=python3-module
@@ -13,4 +13,4 @@ license="Apache-2.0"
homepage="https://github.com/jd/tenacity"
changelog="https://tenacity.readthedocs.io/en/latest/changelog.html"
distfiles="${PYPI_SITE}/t/tenacity/tenacity-${version}.tar.gz"
-checksum=43242a20e3e73291a28bcbcacfd6e000b02d3857a9a9fff56b297a27afdc932f
+checksum=e48c437fdf9340f5666b92cd7990e96bc5fc955e1298baf4a907e3972067a445
next reply other threads:[~2022-09-21 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 17:52 jcgruenhage [this message]
2022-09-21 22:29 ` [PR PATCH] [Merged]: " classabbyamp
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-39404@inbox.vuxu.org \
--to=jcgruenhage@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).