From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-jaraco.functools: update to 3.5.1.
Date: Thu, 18 Aug 2022 16:38:07 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38761@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages python3-jaraco.functools
https://github.com/void-linux/void-packages/pull/38761
python3-jaraco.functools: update to 3.5.1.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64
A patch file from https://github.com/void-linux/void-packages/pull/38761.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-jaraco.functools-38761.patch --]
[-- Type: text/x-diff, Size: 1196 bytes --]
From af2c116cb4c6b886e4fa2d88c4ea937dbdd7927e Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Thu, 18 Aug 2022 20:07:22 +0530
Subject: [PATCH] python3-jaraco.functools: update to 3.5.1.
---
srcpkgs/python3-jaraco.functools/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-jaraco.functools/template b/srcpkgs/python3-jaraco.functools/template
index da6c540ba7a2..6c72f44b4409 100644
--- a/srcpkgs/python3-jaraco.functools/template
+++ b/srcpkgs/python3-jaraco.functools/template
@@ -1,6 +1,6 @@
# Template file for 'python3-jaraco.functools'
pkgname=python3-jaraco.functools
-version=3.5.0
+version=3.5.1
revision=1
wrksrc="jaraco.functools-${version}"
build_style=python3-pep517
@@ -14,7 +14,7 @@ license="MIT"
homepage="https://github.com/jaraco/jaraco.functools"
changelog="https://raw.githubusercontent.com/jaraco/jaraco.functools/master/CHANGES.rst"
distfiles="${PYPI_SITE}/j/jaraco.functools/jaraco.functools-${version}.tar.gz"
-checksum=31e0e93d1027592b7b0bec6ad468db850338981ebee76ba5e212e235f4c7dda0
+checksum=d0adcf91710a0853efe9f23a78fad586bf67df572f0d6d8e0fa36d289ae1c1d9
post_install() {
vlicense LICENSE
next reply other threads:[~2022-08-18 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 14:38 icp1994 [this message]
2022-08-20 22:10 ` [PR PATCH] [Merged]: " paper42
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-38761@inbox.vuxu.org \
--to=icp1994@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).