From: skmpz <skmpz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-regex: update to 2021.11.2.
Date: Thu, 04 Nov 2021 20:04:46 +0100 [thread overview]
Message-ID: <20211104190446.7uLRCNnhKBc_Yh59KR21q0lVBmAWC8SInPObqoGf_X0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33865@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]
There is an updated pull request by skmpz against master on the void-packages repository
https://github.com/skmpz/void-packages python3-regex-2021.11.1
https://github.com/void-linux/void-packages/pull/33865
python3-regex: update to 2021.11.2.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/33865.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-regex-2021.11.1-33865.patch --]
[-- Type: text/x-diff, Size: 1243 bytes --]
From c7d1e89724e24748895363f04b87b274c32ce8c4 Mon Sep 17 00:00:00 2001
From: skmpz <dem.procopiou@gmail.com>
Date: Tue, 2 Nov 2021 07:59:29 +0400
Subject: [PATCH] python3-regex: update to 2021.11.2.
---
srcpkgs/python3-regex/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-regex/template b/srcpkgs/python3-regex/template
index c7b70acbaa73..0309559185a3 100644
--- a/srcpkgs/python3-regex/template
+++ b/srcpkgs/python3-regex/template
@@ -1,17 +1,18 @@
# Template file for 'python3-regex'
pkgname=python3-regex
-version=2021.10.23
+version=2021.11.2
revision=1
wrksrc="regex-${version}"
build_style=python3-module
hostmakedepends="python3-devel python3-setuptools"
makedepends="python3-devel"
+depends="python3"
short_desc="Alternative regular expression module (Python3)"
maintainer="skmpz <dem.procopiou@gmail.com>"
license="CNRI-Python, Apache-2.0"
homepage="https://pypi.org/project/regex/"
distfiles="${PYPI_SITE}/r/regex/regex-${version}.tar.gz"
-checksum=f3f9a91d3cc5e5b0ddf1043c0ae5fa4852f18a1c0050318baf5fc7930ecc1f9c
+checksum=5e85dcfc5d0f374955015ae12c08365b565c6f1eaf36dd182476a4d8e5a1cdb7
do_check() {
(cd build/lib* && python3 -m unittest regex/test_regex.py)
next prev parent reply other threads:[~2021-11-04 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 3:59 [PR PATCH] python3-regex: update to 2021.11.1 skmpz
2021-11-03 16:42 ` Chocimier
2021-11-04 4:00 ` [PR PATCH] [Updated] " skmpz
2021-11-04 4:00 ` python3-regex: update to 2021.11.2 skmpz
2021-11-04 19:04 ` skmpz [this message]
2021-11-05 20:01 ` [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=20211104190446.7uLRCNnhKBc_Yh59KR21q0lVBmAWC8SInPObqoGf_X0@z \
--to=skmpz@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).