Github messages for voidlinux
 help / color / mirror / Atom feed
From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-pycryptodomex: update to 3.11.0.
Date: Wed, 13 Oct 2021 07:58:11 +0200	[thread overview]
Message-ID: <20211013055811.YF4x_JTCaD9Er1fCmVfTP_ehTYOJNPj8FfifjBd-nxE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33516@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

There is an updated 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/33516

python3-pycryptodomex: update to 3.11.0.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [X] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

```
~ ❯ salt --versions | ag dome
  pycryptodome: 3.11.0
```


A patch file from https://github.com/void-linux/void-packages/pull/33516.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pycryptodomex-33516.patch --]
[-- Type: text/x-diff, Size: 1449 bytes --]

From b9170344b33a658bb175c442d8b43e321535b821 Mon Sep 17 00:00:00 2001
From: Antonio Gurgel <antonio@goorzhel.com>
Date: Sat, 9 Oct 2021 14:48:23 -0700
Subject: [PATCH] python3-pycryptodomex: update to 3.11.0.

---
 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 7119d0947f50..5d6855a58c7f 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.10.4
-revision=2
+version=3.11.0
+revision=1
 wrksrc="pycryptodomex-${version}"
 build_style=python3-module
 hostmakedepends="python3-setuptools"
@@ -10,9 +10,9 @@ short_desc="Pycryptodome equivalent that installs under the 'Cryptodome' name"
 maintainer="Antonio Gurgel <antonio@goorzhel.com>"
 license="Public Domain, BSD-2-Clause"
 homepage="https://www.pycryptodome.org/"
-changelog="https://raw.githubusercontent.com/Legrandin/pycryptodome/master/Changelog.rst"
+changelog="https://www.pycryptodome.org/en/latest/src/changelog.html"
 distfiles="${PYPI_SITE}/p/pycryptodomex/pycryptodomex-${version}.tar.gz"
-checksum=acd3498a8ccf8ad20ce7daa5f7f5e6521465eeceb026f28a6adb0228dd9fcc6e
+checksum=0398366656bb55ebdb1d1d493a7175fc48ade449283086db254ac44c7d318d6d
 
 post_install() {
 	vlicense LICENSE.rst

  reply	other threads:[~2021-10-13  5:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13  5:35 [PR PATCH] " Goorzhel
2021-10-13  5:58 ` Goorzhel [this message]
2021-10-13 18:44 ` [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=20211013055811.YF4x_JTCaD9Er1fCmVfTP_ehTYOJNPj8FfifjBd-nxE@z \
    --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).