From: m3tav3rse <m3tav3rse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python-SQLAlchemy: update to 1.4.3.
Date: Sat, 27 Mar 2021 19:35:20 +0100 [thread overview]
Message-ID: <20210327183520.pfkSuzglErEUsK_4OezqVGrLSouDBT5WQas3WDSzm38@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29786@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
There is an updated pull request by m3tav3rse against master on the void-packages repository
https://github.com/m3tav3rse/void-packages SQLAlchemy
https://github.com/void-linux/void-packages/pull/29786
python-SQLAlchemy: update to 1.4.3.
<!-- 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] 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/29786.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-SQLAlchemy-29786.patch --]
[-- Type: text/x-diff, Size: 1462 bytes --]
From b48e09ff391368a706a7f3885bccc3f584d9f97b Mon Sep 17 00:00:00 2001
From: m3tav3rse <mtvrs@tuta.io>
Date: Fri, 26 Mar 2021 21:58:56 +0100
Subject: [PATCH] python-SQLAlchemy: update to 1.4.3.
---
srcpkgs/python-SQLAlchemy/template | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python-SQLAlchemy/template b/srcpkgs/python-SQLAlchemy/template
index b4ff86c2762c..42b7c3c1eeff 100644
--- a/srcpkgs/python-SQLAlchemy/template
+++ b/srcpkgs/python-SQLAlchemy/template
@@ -1,24 +1,28 @@
# Template file for 'python-SQLAlchemy'
pkgname=python-SQLAlchemy
-version=1.3.18
-revision=2
+version=1.4.3
+revision=1
wrksrc="SQLAlchemy-${version}"
build_style=python-module
hostmakedepends="python-setuptools python3-setuptools"
makedepends="python-devel python3-devel"
checkdepends="python3-mock python3-pytest
- python-mock python-pytest"
+ python-mock python-pytest tox"
short_desc="SQL Toolkit and Object Relational Mapper for Python2"
maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://www.sqlalchemy.org"
distfiles="${PYPI_SITE}/S/SQLAlchemy/SQLAlchemy-${version}.tar.gz"
-checksum=da2fb75f64792c1fc64c82313a00c728a7c301efe6a60b7a9fe35b16b4368ce7
+checksum=a719b80b41a900bbcec3cc248616394ebd134043ce5e62185270d785d8a184d3
post_install() {
vlicense LICENSE
}
+do_check() {
+ tox
+}
+
python3-SQLAlchemy_package() {
short_desc="${short_desc/Python2/Python3}"
pkg_install() {
next prev parent reply other threads:[~2021-03-27 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 18:22 [PR PATCH] " m3tav3rse
2021-03-27 18:35 ` m3tav3rse [this message]
2021-03-28 4:34 ` ericonr
2021-06-08 3:19 ` ericonr
2022-05-15 2:13 ` github-actions
2022-05-29 2:13 ` [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=20210327183520.pfkSuzglErEUsK_4OezqVGrLSouDBT5WQas3WDSzm38@z \
--to=m3tav3rse@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).