From: DragonGhost7 <DragonGhost7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-WTForms: update to 3.1.0.
Date: Tue, 21 Nov 2023 06:32:12 +0100 [thread overview]
Message-ID: <20231121053212.Zbxlv3fXWj-fM9shuwOS9qhuxWWUQFCXHjrkU3nW4sw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46816@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
There is an updated pull request by DragonGhost7 against master on the void-packages repository
https://github.com/DragonGhost7/void-packages wtforms
https://github.com/void-linux/void-packages/pull/46816
python3-WTForms: update to 3.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-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- armv6l-musl
- armv7l
- x86_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/46816.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-wtforms-46816.patch --]
[-- Type: text/x-diff, Size: 1621 bytes --]
From 7b207fa007384385f52629448f49488fa7d38577 Mon Sep 17 00:00:00 2001
From: DragonGhost7 <darkiridiumghost@gmail.com>
Date: Sat, 21 Oct 2023 12:55:42 -0400
Subject: [PATCH] python3-WTForms: update to 3.1.0.
---
srcpkgs/python3-WTForms/template | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/srcpkgs/python3-WTForms/template b/srcpkgs/python3-WTForms/template
index f23c7bf0bf2a5..0844d08859a84 100644
--- a/srcpkgs/python3-WTForms/template
+++ b/srcpkgs/python3-WTForms/template
@@ -1,18 +1,18 @@
# Template file for 'python3-WTForms'
pkgname=python3-WTForms
-version=3.0.1
-revision=3
-build_style=python3-module
-hostmakedepends="python3-setuptools python3-wheel python3-Babel"
+version=3.1.0
+revision=1
+build_style=python3-pep517
+hostmakedepends="python3-setuptools hatchling python3-Babel"
depends="python3 python3-MarkupSafe python3-email-validator"
checkdepends="python3-pytest ${depends}"
short_desc="Forms validation and rendering library for Python3"
maintainer="DragonGhost7 <darkiridiumghost@gmail.com>"
license="BSD-3-Clause"
homepage="http://wtforms.simplecodes.com/"
-#changelog="https://raw.githubusercontent.com/wtforms/wtforms/master/CHANGES.rst"
-distfiles="${PYPI_SITE}/W/WTForms/WTForms-${version}.tar.gz"
-checksum=6b351bbb12dd58af57ffef05bc78425d08d1914e0fd68ee14143b7ade023c5bc
+changelog="https://raw.githubusercontent.com/wtforms/wtforms/master/CHANGES.rst"
+distfiles="${PYPI_SITE}/W/WTForms/wtforms-${version}.tar.gz"
+checksum=4edd15771630289a5fa343d58822f72749822ca5a39dd33f92ee917cf72b954b
post_install() {
vlicense LICENSE.rst LICENSE
next prev parent reply other threads:[~2023-11-21 5:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 16:59 [PR PATCH] " DragonGhost7
2023-11-16 13:42 ` [PR REVIEW] " ahesford
2023-11-16 13:42 ` ahesford
2023-11-21 5:32 ` DragonGhost7 [this message]
2023-11-21 5:32 ` DragonGhost7
2023-11-21 11:31 ` [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=20231121053212.Zbxlv3fXWj-fM9shuwOS9qhuxWWUQFCXHjrkU3nW4sw@z \
--to=dragonghost7@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).