From: Eloitor <Eloitor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-PGPy: update to 0.6.0.
Date: Thu, 09 Feb 2023 09:46:43 +0100 [thread overview]
Message-ID: <20230209084643.Vo5tPMCzVUhh1hmlt_a8KBu1016Y0KaD-IOpmXd86qk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42106@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
There is an updated pull request by Eloitor against master on the void-packages repository
https://github.com/Eloitor/void-packages PGPy
https://github.com/void-linux/void-packages/pull/42106
python3-PGPy: update to 0.6.0.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/42106.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-PGPy-42106.patch --]
[-- Type: text/x-diff, Size: 1293 bytes --]
From b99f3944fc90f541e0e3364d47222602c6c2e9c1 Mon Sep 17 00:00:00 2001
From: Eloi Torrents <eloitor@disroot.org>
Date: Mon, 6 Feb 2023 10:31:09 +0100
Subject: [PATCH] python3-PGPy: update to 0.6.0.
---
srcpkgs/python3-PGPy/template | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/python3-PGPy/template b/srcpkgs/python3-PGPy/template
index 5268c19777ad..ee059076e373 100644
--- a/srcpkgs/python3-PGPy/template
+++ b/srcpkgs/python3-PGPy/template
@@ -1,18 +1,17 @@
# Template file for 'python3-PGPy'
pkgname=python3-PGPy
-version=0.5.4
-revision=2
+version=0.6.0
+revision=1
build_style=python3-module
hostmakedepends="python3-setuptools python3-wheel"
depends="python3-cryptography python3-pyasn1 python3-six"
+checkdepends="python3-pytest python3-progressbar $depends"
short_desc="Pretty Good Privacy for Python"
maintainer="Anjandev Momi <anjan@momi.ca>"
license="BSD-3-Clause"
homepage="https://github.com/SecurityInnovation/PGPy"
distfiles="https://github.com/SecurityInnovation/PGPy/archive/v${version}.tar.gz"
-checksum=beb2e7745ddebf85a24239aa681fa83a9ab8f8867d7ac55351fb0732279ac4fa
-# requires progressbar
-make_check=no
+checksum=33028fc2c47718a9215311bb22d6fed042074afbc91bf4e9764fdf0df54fc2b3
post_install() {
vlicense LICENSE
next prev parent reply other threads:[~2023-02-09 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 9:23 [PR PATCH] " Eloitor
2023-02-08 16:44 ` [PR REVIEW] " ahesford
2023-02-09 8:46 ` Eloitor [this message]
2023-02-09 11:19 ` [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=20230209084643.Vo5tPMCzVUhh1hmlt_a8KBu1016Y0KaD-IOpmXd86qk@z \
--to=eloitor@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).