Github messages for voidlinux
 help / color / mirror / Atom feed
From: skmpz <skmpz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-regex: update to 2021.7.6.
Date: Thu, 22 Jul 2021 10:23:47 +0200	[thread overview]
Message-ID: <20210722082347.7L-ub21vFoG7wkVrnVDE2JICB6oLgwzikoxdvRdT2vk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31798@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1612 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.7.1
https://github.com/void-linux/void-packages/pull/31798

python3-regex: update to 2021.7.6.
<!-- 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/31798.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-regex-2021.7.1-31798.patch --]
[-- Type: text/x-diff, Size: 1091 bytes --]

From d2056ff5969667c1288c5a7e9e1615e385b2a7f7 Mon Sep 17 00:00:00 2001
From: skmpz <dem.procopiou@gmail.com>
Date: Sun, 4 Jul 2021 23:00:56 +0400
Subject: [PATCH] python3-regex: update to 2021.7.6.

---
 srcpkgs/python3-regex/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/python3-regex/template b/srcpkgs/python3-regex/template
index 908e96454479..d4e7636810e9 100644
--- a/srcpkgs/python3-regex/template
+++ b/srcpkgs/python3-regex/template
@@ -1,6 +1,6 @@
 # Template file for 'python3-regex'
 pkgname=python3-regex
-version=2021.4.4
+version=2021.7.6
 revision=1
 wrksrc="regex-${version}"
 build_style=python3-module
@@ -11,7 +11,7 @@ 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=52ba3d3f9b942c49d7e4bc105bb28551c44065f139a65062ab7912bef10c9afb
+checksum=8394e266005f2d8c6f0bc6780001f7afa3ef81a7a2111fa35058ded6fce79e4d
 
 do_check() {
 	(cd build/lib* && python3 -m unittest regex/test_regex.py)

  parent reply	other threads:[~2021-07-22  8:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-04 19:06 [PR PATCH] python3-regex: update to 2021.7.1 skmpz
2021-07-17  4:03 ` ericonr
2021-07-22  8:22 ` [PR PATCH] [Updated] " skmpz
2021-07-22  8:22 ` python3-regex: update to 2021.7.6 skmpz
2021-07-22  8:23 ` skmpz [this message]
2021-07-22 14:33 ` [PR PATCH] [Merged]: " ahesford

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=20210722082347.7L-ub21vFoG7wkVrnVDE2JICB6oLgwzikoxdvRdT2vk@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).