From: Luciogi <Luciogi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-SQLAlchemy2: update to 2.0.23.
Date: Fri, 17 Nov 2023 19:42:22 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47286@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
There is a new pull request by Luciogi against master on the void-packages repository
https://github.com/Luciogi/void-packages py3-SQLAlchemy2
https://github.com/void-linux/void-packages/pull/47286
python3-SQLAlchemy2: update to 2.0.23.
#### 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/47286.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-py3-SQLAlchemy2-47286.patch --]
[-- Type: text/x-diff, Size: 1211 bytes --]
From e2e8c2b5ca69dc8b85502d0e2ee077121073a53b Mon Sep 17 00:00:00 2001
From: Luciogi <lucigithubcommit@skiff.com>
Date: Fri, 17 Nov 2023 23:38:12 +0500
Subject: [PATCH] python3-SQLAlchemy2: update to 2.0.23.
---
srcpkgs/python3-SQLAlchemy2/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-SQLAlchemy2/template b/srcpkgs/python3-SQLAlchemy2/template
index b745692dc1b34..24793492f83e1 100644
--- a/srcpkgs/python3-SQLAlchemy2/template
+++ b/srcpkgs/python3-SQLAlchemy2/template
@@ -1,7 +1,7 @@
# Template file for 'python3-SQLAlchemy2'
pkgname=python3-SQLAlchemy2
-version=2.0.16
-revision=2
+version=2.0.23
+revision=1
build_style=python3-pep517
make_install_target="dist/SQLAlchemy-${version}-*-*-*.whl"
hostmakedepends="python3-setuptools python3-Cython python3-wheel"
@@ -14,7 +14,7 @@ license="MIT"
homepage="https://www.sqlalchemy.org"
changelog="https://docs.sqlalchemy.org/en/20/changelog/"
distfiles="${PYPI_SITE}/S/SQLAlchemy/SQLAlchemy-${version}.tar.gz"
-checksum=1e2caba78e7d1f5003e88817b7a1754d4e58f4a8f956dc423bf8e304c568ab09
+checksum=c1bda93cbbe4aa2aa0aa8655c5aeda505cd219ff3e8da91d1d329e143e4aff69
conflicts="python3-SQLAlchemy"
next reply other threads:[~2023-11-17 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 18:42 Luciogi [this message]
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-47286@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).