From: DragonGhost7 <DragonGhost7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-email-validator: update to 2.0.0.
Date: Tue, 21 Nov 2023 06:28:24 +0100 [thread overview]
Message-ID: <20231121052824.JLMUdMvE4eDF6q6DYVwjx7YN9XyZwXPSLMCBiLA4VlI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46781@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
There is an updated pull request by DragonGhost7 against master on the void-packages repository
https://github.com/DragonGhost7/void-packages email_validator
https://github.com/void-linux/void-packages/pull/46781
python3-email-validator: update to 2.0.0.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### 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):
- i686
- x86_64-musl
- armv6l-musl
A patch file from https://github.com/void-linux/void-packages/pull/46781.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-email_validator-46781.patch --]
[-- Type: text/x-diff, Size: 1574 bytes --]
From d38bcf06aa279c8d2e3867edfa8cd76a654b6a03 Mon Sep 17 00:00:00 2001
From: DragonGhost7 <darkiridiumghost@gmail.com>
Date: Thu, 19 Oct 2023 15:50:46 -0400
Subject: [PATCH] python3-email-validator: update to 2.0.0.
---
srcpkgs/python3-email-validator/template | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/python3-email-validator/template b/srcpkgs/python3-email-validator/template
index 69628ad1e35db..9534a0c875b59 100644
--- a/srcpkgs/python3-email-validator/template
+++ b/srcpkgs/python3-email-validator/template
@@ -1,20 +1,19 @@
# Template file for 'python3-email-validator'
pkgname=python3-email-validator
-version=1.3.0
-revision=3
+version=2.0.0
+revision=1
build_style=python3-module
hostmakedepends="python3-setuptools"
makedepends="python3"
depends="python3-idna python3-dnspython"
-checkdepends="python3-pytest"
+checkdepends="python3-pytest $depends"
short_desc="Robust email address syntax and deliverability validation library"
maintainer="DragonGhost7 <darkiridiumghost@gmail.com>"
license="CC0-1.0"
homepage="https://github.com/JoshData/python-email-validator"
changelog="https://raw.githubusercontent.com/JoshData/python-email-validator/main/CHANGELOG.md"
distfiles="https://github.com/JoshData/python-email-validator/archive/refs/tags/v${version}.tar.gz"
-checksum=1f5b38b5f6b8455468f2c557e887c442d455931ee1523c6eb40c6f7ce119d99b
-make_check=no #no tests folder is present in archives
+checksum=0cd656b4c2cba10bcb518808f800bdde74af0c01a2522a9d475b3b1954d98f01
post_install() {
vlicense LICENSE
next prev parent reply other threads:[~2023-11-21 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 19:53 [PR PATCH] " DragonGhost7
2023-11-16 13:49 ` [PR REVIEW] " ahesford
2023-11-21 5:28 ` DragonGhost7 [this message]
2023-11-29 11:42 ` ahesford
2024-02-28 1:44 ` github-actions
2024-03-13 1:45 ` [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=20231121052824.JLMUdMvE4eDF6q6DYVwjx7YN9XyZwXPSLMCBiLA4VlI@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).