From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-pycryptodomex: update to 3.12.0.
Date: Sun, 12 Dec 2021 22:48:52 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34497@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 501 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/34497
python3-pycryptodomex: update to 3.12.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
```
$ salt --versions | grep dome
pycryptodome: 3.12.0
```
Salt apply ran uneventfully.
A patch file from https://github.com/void-linux/void-packages/pull/34497.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pycryptodomex-34497.patch --]
[-- Type: text/x-diff, Size: 1297 bytes --]
From 43f485e9044e58ff554aa8ba4a292125f1eefd0e Mon Sep 17 00:00:00 2001
From: Antonio Gurgel <antonio@goorzhel.com>
Date: Mon, 6 Dec 2021 19:42:30 -0800
Subject: [PATCH] python3-pycryptodomex: update to 3.12.0.
---
srcpkgs/python3-pycryptodomex/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-pycryptodomex/template b/srcpkgs/python3-pycryptodomex/template
index 5d6855a58c7f..30bd5a5d5e0c 100644
--- a/srcpkgs/python3-pycryptodomex/template
+++ b/srcpkgs/python3-pycryptodomex/template
@@ -1,6 +1,6 @@
# Template file for 'python3-pycryptodomex'
pkgname=python3-pycryptodomex
-version=3.11.0
+version=3.12.0
revision=1
wrksrc="pycryptodomex-${version}"
build_style=python3-module
@@ -11,8 +11,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}.tar.gz"
-checksum=0398366656bb55ebdb1d1d493a7175fc48ade449283086db254ac44c7d318d6d
+distfiles="${PYPI_SITE}/p/pycryptodomex/pycryptodomex-${version}.zip"
+checksum=922e9dac0166e4617e5c7980d2cff6912a6eb5cb5c13e7ece222438650bd7f66
post_install() {
vlicense LICENSE.rst
next reply other threads:[~2021-12-12 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 21:48 Goorzhel [this message]
2021-12-15 0:49 ` [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-34497@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).