Github messages for voidlinux
 help / color / mirror / Atom feed
From: ndowens <ndowens@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-saml2: update to 6.4.1.
Date: Wed, 09 Dec 2020 22:19:10 +0100	[thread overview]
Message-ID: <20201209211910.Oz4uaf3ESphG1DR4SEedjJ6deQ3Sh7MPurs1OBe2lYQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27050@inbox.vuxu.org>

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

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

https://github.com/ndowens/void-packages saml
https://github.com/void-linux/void-packages/pull/27050

python3-saml2: update to 6.4.1.
This fixes byte-compiling upon install

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

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

From 809ca23c4c02b8505a279a3dd47e5b869743ce75 Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens@artixlinux.org>
Date: Wed, 9 Dec 2020 09:56:13 -0600
Subject: [PATCH] python3-saml2: update to 6.4.1.

---
 srcpkgs/python3-saml2/template | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/python3-saml2/template b/srcpkgs/python3-saml2/template
index 5506ce0828f..13190c53ffc 100644
--- a/srcpkgs/python3-saml2/template
+++ b/srcpkgs/python3-saml2/template
@@ -1,15 +1,22 @@
 # Template file for 'python3-saml2'
 pkgname=python3-saml2
-version=5.0.0
-revision=2
+version=6.4.1
+revision=1
 wrksrc="pysaml2-${version}"
 build_style=python3-module
 hostmakedepends="python3-setuptools"
 depends="python3-cryptography python3-openssl python3-dateutil python3-pytz
  python3-requests python3-six python3-defusedxml"
+checkdepends="tox xmlsec1 xmlsec1-devel"
 short_desc="Python3 implementation of SAML Version 2 Standard"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="Apache-2.0"
 homepage="https://github.com/IdentityPython/pysaml2"
-distfiles="${PYPI_SITE}/p/pysaml2/pysaml2-${version}.tar.gz"
-checksum=deea75b252b5ead821f12ce01e9d88b0f6fbcde322c1595dcbb06f9660af0cc1
+distfiles="https://github.com/IdentityPython/pysaml2/archive/v${version}.tar.gz"
+checksum=341fe81e1fdff72e6082ba81645a9b75dab7482cf9b878f566d023311169f8c0
+
+do_check() {
+	# Remove un-used python versions
+	vsed -e '/py36/,/py38/d' -e '/pypy3/d' -i tox.ini
+	tox -c tox.ini
+}

  parent reply	other threads:[~2020-12-09 21:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 16:02 [PR PATCH] " ndowens
2020-12-09 16:04 ` [PR REVIEW] " ericonr
2020-12-09 16:04 ` ericonr
2020-12-09 17:41 ` ndowens
2020-12-09 20:58 ` ericonr
2020-12-09 21:02 ` [PR REVIEW] " ahesford
2020-12-09 21:19 ` ndowens [this message]
2020-12-09 21:21 ` ndowens
2020-12-09 21:22 ` ndowens
2020-12-09 21:27 ` ndowens
2020-12-10  4:13 ` [PR PATCH] [Closed]: " ahesford
2020-12-10  4:19 ` 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=20201209211910.Oz4uaf3ESphG1DR4SEedjJ6deQ3Sh7MPurs1OBe2lYQ@z \
    --to=ndowens@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).