From: hamlolum <hamlolum@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-mysqlclient: update to 2.1.0.
Date: Thu, 20 Jan 2022 12:02:29 +0100 [thread overview]
Message-ID: <20220120110229.s8_u2WtNn5K00cvmzU_rSe7JWj7kwGVPkMjMJzs1Yq4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35062@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
There is an updated pull request by hamlolum against master on the void-packages repository
https://github.com/hamlolum/void-packages mysqlclient
https://github.com/void-linux/void-packages/pull/35062
python3-mysqlclient: 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/35062.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mysqlclient-35062.patch --]
[-- Type: text/x-diff, Size: 1341 bytes --]
From eb097f93521d7245b68bdc101de6eed586ef64ed Mon Sep 17 00:00:00 2001
From: hamlolum <hamlolum@tilde.club>
Date: Sat, 15 Jan 2022 16:03:41 +0530
Subject: [PATCH] python3-mysqlclient: update to 2.1.0.
---
srcpkgs/python3-mysqlclient/template | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-mysqlclient/template b/srcpkgs/python3-mysqlclient/template
index 696dddf7f595..ebd8bbf069be 100644
--- a/srcpkgs/python3-mysqlclient/template
+++ b/srcpkgs/python3-mysqlclient/template
@@ -1,7 +1,7 @@
# Template file for 'python3-mysqlclient'
pkgname=python3-mysqlclient
-version=1.3.14
-revision=8
+version=2.1.0
+revision=1
wrksrc="mysqlclient-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools"
@@ -10,6 +10,7 @@ depends="python3"
short_desc="Python3 interface to MySQL/MariaDB"
maintainer="Alin Dobre <alin.dobre@outlook.com>"
license="GPL-2.0-or-later"
-homepage="https://github.com/PyMySQL/mysqlclient-python"
+homepage="https://github.com/PyMySQL/mysqlclient"
+changelog="https://raw.githubusercontent.com/PyMySQL/mysqlclient/main/HISTORY.rst"
distfiles="${PYPI_SITE}/m/mysqlclient/mysqlclient-${version}.tar.gz"
-checksum=3981ae9ce545901a36a8b7aed76ed02960a429f75dc53b7ad77fb2f9ab7cd56b
+checksum=973235686f1b720536d417bf0a0d39b4ab3d5086b2b6ad5e6752393428c02b12
next prev parent reply other threads:[~2022-01-20 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 10:35 [PR PATCH] " hamlolum
2022-01-20 0:59 ` [PR REVIEW] " paper42
2022-01-20 6:55 ` hamlolum
2022-01-20 6:56 ` [PR PATCH] [Updated] " hamlolum
2022-01-20 6:57 ` [PR REVIEW] " hamlolum
2022-01-20 7:02 ` hamlolum
2022-01-20 7:48 ` [PR PATCH] [Updated] " hamlolum
2022-01-20 9:19 ` [PR REVIEW] " paper42
2022-01-20 9:23 ` paper42
2022-01-20 9:32 ` Johnnynator
2022-01-20 11:02 ` hamlolum [this message]
2022-01-20 11:03 ` [PR REVIEW] " hamlolum
2022-06-22 2:14 ` github-actions
2022-07-07 2:14 ` [PR PATCH] [Closed]: " github-actions
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=20220120110229.s8_u2WtNn5K00cvmzU_rSe7JWj7kwGVPkMjMJzs1Yq4@z \
--to=hamlolum@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).