From: shak-mar <shak-mar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-PGPy: update to 0.5.4
Date: Wed, 06 Jul 2022 20:00:29 +0200 [thread overview]
Message-ID: <20220706180029.ivlbF69KFmIszRdKFo2dC_qWVC1mnC6xjhxEzFRS0qU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37895@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
There is an updated pull request by shak-mar against master on the void-packages repository
https://github.com/shak-mar/void-packages update-python3-PGPy-to-0.5.4
https://github.com/void-linux/void-packages/pull/37895
python3-PGPy: update to 0.5.4
The previous version of python3-PGPy (0.5.3) is not compatible with python 3.10 because of the `collections.MutableMapping` deprecation. You can reproduce the issue by installing `python3-PGPy`, then running `python3` and within that, `import pgpy`.
#### Testing the changes
- I tested the changes in this PR: **briefly**
A patch file from https://github.com/void-linux/void-packages/pull/37895.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-python3-PGPy-to-0.5.4-37895.patch --]
[-- Type: text/x-diff, Size: 1270 bytes --]
From 3fe2a4aa2e0976f9352caa11de126637b97f7d01 Mon Sep 17 00:00:00 2001
From: Michael Struwe <michaelstruwe@gmx.net>
Date: Wed, 6 Jul 2022 15:17:20 +0200
Subject: [PATCH] python3-PGPy: update to 0.5.4
---
srcpkgs/python3-PGPy/template | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-PGPy/template b/srcpkgs/python3-PGPy/template
index fa73d46876ce..7de7c554b74f 100644
--- a/srcpkgs/python3-PGPy/template
+++ b/srcpkgs/python3-PGPy/template
@@ -1,7 +1,7 @@
# Template file for 'python3-PGPy'
pkgname=python3-PGPy
-version=0.5.3
-revision=3
+version=0.5.4
+revision=1
wrksrc=PGPy-${version}
build_style=python3-module
hostmakedepends="python3-setuptools python3-wheel"
@@ -10,8 +10,10 @@ short_desc="Pretty Good Privacy for Python"
maintainer="Anjandev Momi <anjan@momi.ca>"
license="BSD-3-Clause"
homepage="https://github.com/SecurityInnovation/PGPy"
-distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=5f56454c92fe0c242397166df4618183992d6786c2568cbd21c4090344cf2635
+distfiles="https://github.com/SecurityInnovation/PGPy/archive/v${version}.tar.gz"
+checksum=beb2e7745ddebf85a24239aa681fa83a9ab8f8867d7ac55351fb0732279ac4fa
+# requires progressbar
+make_check=no
post_install() {
vlicense LICENSE
next prev parent reply other threads:[~2022-07-06 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 13:29 [PR PATCH] " shak-mar
2022-07-06 14:41 ` [PR REVIEW] " classabbyamp
2022-07-06 16:30 ` [PR PATCH] [Updated] " shak-mar
2022-07-06 16:33 ` shak-mar
2022-07-06 16:45 ` classabbyamp
2022-07-06 18:00 ` shak-mar [this message]
2022-07-06 20:14 ` shak-mar
2022-07-07 17:55 ` [PR PATCH] [Merged]: " classabbyamp
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=20220706180029.ivlbF69KFmIszRdKFo2dC_qWVC1mnC6xjhxEzFRS0qU@z \
--to=shak-mar@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).