From: Luciogi <Luciogi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-PyHamcrest: update to 2.1.0.
Date: Fri, 17 Nov 2023 18:20:13 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47284@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
There is a new pull request by Luciogi against master on the void-packages repository
https://github.com/Luciogi/void-packages py3-pyhamcrest
https://github.com/void-linux/void-packages/pull/47284
python3-PyHamcrest: update to 2.1.0.
#### Testing the changes
- I tested the changes in this PR: **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/47284.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-py3-pyhamcrest-47284.patch --]
[-- Type: text/x-diff, Size: 1151 bytes --]
From 688a91ff66b5873469b1cbbe410532539a1d2c13 Mon Sep 17 00:00:00 2001
From: Luciogi <lucigithubcommit@skiff.com>
Date: Fri, 17 Nov 2023 22:18:50 +0500
Subject: [PATCH] python3-PyHamcrest: update to 2.1.0.
---
srcpkgs/python3-PyHamcrest/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-PyHamcrest/template b/srcpkgs/python3-PyHamcrest/template
index e7c7bb288c259..5d05fe8955487 100644
--- a/srcpkgs/python3-PyHamcrest/template
+++ b/srcpkgs/python3-PyHamcrest/template
@@ -1,7 +1,7 @@
# Template file for 'python3-PyHamcrest'
pkgname=python3-PyHamcrest
-version=2.0.4
-revision=2
+version=2.1.0
+revision=1
build_style=python3-pep517
hostmakedepends="hatch-vcs"
depends="python3"
@@ -11,7 +11,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="BSD-3-Clause"
homepage="https://github.com/hamcrest/PyHamcrest"
distfiles="${PYPI_SITE}/p/pyhamcrest/pyhamcrest-${version}.tar.gz"
-checksum=b5d9ce6b977696286cf232ce2adf8969b4d0b045975b0936ac9005e84e67e9c1
+checksum=c6acbec0923d0cb7e72c22af1926f3e7c97b8e8d69fc7498eabacaf7c975bd9c
make_check_pre="env PYTHONPATH=src"
post_install() {
next reply other threads:[~2023-11-17 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 17:20 Luciogi [this message]
2023-11-17 17:39 ` [PR REVIEW] " paper42
2023-11-17 17:51 ` [PR PATCH] [Updated] " Luciogi
2023-12-03 20:01 ` [PR PATCH] [Merged]: " Duncaen
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-47284@inbox.vuxu.org \
--to=luciogi@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).