From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-pycryptodomex: update to 3.15.0.
Date: Fri, 24 Jun 2022 07:03:51 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37666@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 469 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/37666
python3-pycryptodomex: update to 3.15.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
```
$ salt --versions | grep dome
pycryptodome: 3.15.0
```
A patch file from https://github.com/void-linux/void-packages/pull/37666.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pycryptodomex-37666.patch --]
[-- Type: text/x-diff, Size: 1173 bytes --]
From 69fa462873c18bff942ed23e8803a0d66da697a5 Mon Sep 17 00:00:00 2001
From: Antonio Gurgel <antonio@goorzhel.com>
Date: Thu, 23 Jun 2022 22:00:47 -0700
Subject: [PATCH] python3-pycryptodomex: update to 3.15.0.
---
srcpkgs/python3-pycryptodomex/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-pycryptodomex/template b/srcpkgs/python3-pycryptodomex/template
index c6e0618f9640..622501a2e2ab 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.14.1
+version=3.15.0
revision=1
wrksrc="pycryptodomex-${version}"
build_style=python3-module
@@ -13,7 +13,7 @@ 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=2ce76ed0081fd6ac8c74edc75b9d14eca2064173af79843c24fa62573263c1f2
+checksum=7341f1bb2dadb0d1a0047f34c3a58208a92423cdbd3244d998e4b28df5eac0ed
post_install() {
vlicense LICENSE.rst
next reply other threads:[~2022-06-24 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 5:03 Goorzhel [this message]
2022-06-26 1:15 ` [PR PATCH] [Merged]: " sgn
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-37666@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).