Github messages for voidlinux
 help / color / mirror / Atom feed
From: FollieHiyuki <FollieHiyuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-PyJWT: update to 2.0.1 + fix information
Date: Fri, 19 Feb 2021 18:03:15 +0100	[thread overview]
Message-ID: <20210219170315.JXykSti8WC0xbHdlmAGu6ZUzgLr0RqEcRnaLEOBJfH4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28838@inbox.vuxu.org>

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

There is an updated pull request by FollieHiyuki against master on the void-packages repository

https://github.com/FollieHiyuki/void-packages pyjwt
https://github.com/void-linux/void-packages/pull/28838

python3-PyJWT: update to 2.0.1 + fix information
<!-- 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->

There are test failures with ssl. I have no idea what to do with it though.

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

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

From f0a9e18a44e09fbf1656ae7fcf2494bdb54cd9e2 Mon Sep 17 00:00:00 2001
From: FollieHiyuki <folliekazetani@protonmail.com>
Date: Thu, 18 Feb 2021 16:32:46 +0300
Subject: [PATCH] python3-PyJWT: update to 2.0.1 + fix information

Also drop python2 dependency
---
 srcpkgs/python3-PyJWT/template | 24 +++++++++++++++---------
 1 file changed, 15 insertions(+), 9 deletions(-)

diff --git a/srcpkgs/python3-PyJWT/template b/srcpkgs/python3-PyJWT/template
index d8137fd5ec6..e751ddfa9be 100644
--- a/srcpkgs/python3-PyJWT/template
+++ b/srcpkgs/python3-PyJWT/template
@@ -1,15 +1,21 @@
 # Template file for 'python3-PyJWT'
 pkgname=python3-PyJWT
-version=2.0.0
+version=2.0.1
 revision=1
-wrksrc="PyJWT-${version}"
+wrksrc="pyjwt-${version}"
 build_style=python3-module
 hostmakedepends="python3-setuptools"
-depends="python"
-checkdepends="python3-pytest"
-short_desc="Platform independent file lock"
+depends="python3"
+checkdepends="python3-pytest python3-cryptography"
+short_desc="Python implementation of RFC 7519"
 maintainer="fosslinux <fosslinux@aussies.space>"
-license="Unlicense"
-homepage="https://filelock.readthedocs.io/en/latest/"
-distfiles="${PYPI_SITE}/P/PyJWT/PyJWT-${version}.tar.gz"
-checksum=7a2b271c6dac2fda9e0c33d176c4253faba2c6c6b3a99c7f28a32c3c97522779
+license="MIT"
+homepage="https://pyjwt.readthedocs.io/"
+distfiles="https://github.com/jpadilla/pyjwt/archive/${version}.tar.gz"
+checksum=63f296b42b4107a9e3ba4994d2d575ee0d05b9a55f433a3f46febfc4ee381ad1
+# Re-enable when switching to OpenSSL
+make_check=no
+
+post_install() {
+	vlicense LICENSE
+}

  parent reply	other threads:[~2021-02-19 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 13:37 [PR PATCH] " FollieHiyuki
2021-02-19 15:19 ` ericonr
2021-02-19 16:34 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-19 16:35 ` FollieHiyuki
2021-02-19 17:03 ` FollieHiyuki [this message]
2021-02-19 17:19 ` FollieHiyuki
2021-02-19 17:21 ` FollieHiyuki
2021-02-19 17:27 ` ericonr
2021-02-19 17:27 ` ericonr
2021-02-19 17:35 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-19 17:38 ` FollieHiyuki
2021-02-20  4:44 ` [PR PATCH] [Merged]: " ericonr

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=20210219170315.JXykSti8WC0xbHdlmAGu6ZUzgLr0RqEcRnaLEOBJfH4@z \
    --to=folliehiyuki@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).