From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-pycryptodomex: update to 3.14.1.
Date: Mon, 07 Feb 2022 02:18:22 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35453@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
There is a new pull request by Goorzhel against master on the void-packages repository
https://github.com/Goorzhel/void-packages python3-pycryptodomex
https://github.com/void-linux/void-packages/pull/35453
python3-pycryptodomex: update to 3.14.1.
#### Testing the changes
- I tested the changes in this PR: **briefly**
```
❯ salt --versions | ag dome
pycryptodome: 3.14.1
❯ salt '*' state.apply
<...>
❯ echo $?
0
```
A patch file from https://github.com/void-linux/void-packages/pull/35453.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pycryptodomex-35453.patch --]
[-- Type: text/x-diff, Size: 1349 bytes --]
From f622c37bc96dd0ae5cef008ca2e59be80e0db8e2 Mon Sep 17 00:00:00 2001
From: Antonio Gurgel <antonio@goorzhel.com>
Date: Sun, 6 Feb 2022 16:55:48 -0800
Subject: [PATCH] python3-pycryptodomex: update to 3.14.1.
---
srcpkgs/python3-pycryptodomex/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-pycryptodomex/template b/srcpkgs/python3-pycryptodomex/template
index fe1357e30570..c6e0618f9640 100644
--- a/srcpkgs/python3-pycryptodomex/template
+++ b/srcpkgs/python3-pycryptodomex/template
@@ -1,7 +1,7 @@
# Template file for 'python3-pycryptodomex'
pkgname=python3-pycryptodomex
-version=3.12.0
-revision=2
+version=3.14.1
+revision=1
wrksrc="pycryptodomex-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools"
@@ -12,8 +12,8 @@ maintainer="Antonio Gurgel <antonio@goorzhel.com>"
license="Public Domain, BSD-2-Clause"
homepage="https://www.pycryptodome.org/"
changelog="https://www.pycryptodome.org/en/latest/src/changelog.html"
-distfiles="${PYPI_SITE}/p/pycryptodomex/pycryptodomex-${version}.zip"
-checksum=922e9dac0166e4617e5c7980d2cff6912a6eb5cb5c13e7ece222438650bd7f66
+distfiles="${PYPI_SITE}/p/pycryptodomex/pycryptodomex-${version}.tar.gz"
+checksum=2ce76ed0081fd6ac8c74edc75b9d14eca2064173af79843c24fa62573263c1f2
post_install() {
vlicense LICENSE.rst
next reply other threads:[~2022-02-07 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 1:18 Goorzhel [this message]
2022-02-17 23:28 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35453@inbox.vuxu.org \
--to=goorzhel@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).