From: aurieh <aurieh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-pynacl: update to 1.5.0
Date: Fri, 21 Oct 2022 01:45:53 +0200 [thread overview]
Message-ID: <20221020234553.RcXB7dVjdJOlqc3vRXjMMmV6PKlcgRNJ2kXOdN5Fxzw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40066@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
There is an updated pull request by aurieh against master on the void-packages repository
https://github.com/aurieh/void-packages python3-pynacl-1.5.0
https://github.com/void-linux/void-packages/pull/40066
python3-pynacl: update to 1.5.0
[Changelog](https://github.com/pyca/pynacl/blob/main/CHANGELOG.rst#150-2022-01-07): no breaking changes relevant to Void.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### 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/40066.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pynacl-1.5.0-40066.patch --]
[-- Type: text/x-diff, Size: 1460 bytes --]
From 4e110e4bc285667f3b3af2fea2c1926f251100c1 Mon Sep 17 00:00:00 2001
From: Auri <me@aurieh.me>
Date: Thu, 20 Oct 2022 23:10:21 +0000
Subject: [PATCH] python3-pynacl: update to 1.5.0
---
srcpkgs/python3-pynacl/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/python3-pynacl/template b/srcpkgs/python3-pynacl/template
index 1ad1ea06883f..9e2841761822 100644
--- a/srcpkgs/python3-pynacl/template
+++ b/srcpkgs/python3-pynacl/template
@@ -1,20 +1,20 @@
# Template file for 'python3-pynacl'
pkgname=python3-pynacl
-version=1.4.0
-revision=2
+version=1.5.0
+revision=1
wrksrc="PyNaCl-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools python3-cffi python3-wheel"
makedepends="python3-devel python3-cffi libsodium-devel"
-depends="python3-cffi python3-six"
-checkdepends="${depends}"
+depends="python3-cffi"
+checkdepends="${depends} python3-pytest python3-hypothesis"
short_desc="Python3 binding to the Networking and Cryptography (NaCl) library"
maintainer="Orphaned <orphan@voidlinux.org>"
license="Apache-2.0"
homepage="https://github.com/pyca/pynacl/"
changelog="https://raw.githubusercontent.com/pyca/pynacl/master/CHANGELOG.rst"
distfiles="${PYPI_SITE}/P/PyNaCl/PyNaCl-${version}.tar.gz"
-checksum=54e9a2c849c742006516ad56a88f5c74bf2ce92c9f67435187c3c5953b346505
+checksum=8ac7448f09ab85811607bdd21ec2464495ac8b7c66d146bf545b0f08fb9220ba
export SODIUM_INSTALL=system
next prev parent reply other threads:[~2022-10-20 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 23:25 [PR PATCH] " aurieh
2022-10-20 23:41 ` [PR REVIEW] " paper42
2022-10-20 23:44 ` aurieh
2022-10-20 23:45 ` aurieh [this message]
2022-10-23 1:16 ` [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=20221020234553.RcXB7dVjdJOlqc3vRXjMMmV6PKlcgRNJ2kXOdN5Fxzw@z \
--to=aurieh@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).