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-jsonschema: update to 3.2.0
Date: Thu, 17 Dec 2020 21:36:25 +0100	[thread overview]
Message-ID: <20201217203625.pjeYcQNK6juVlkASgNa5EcYC7PBgs-7w9AWWRL5ho6U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26806@inbox.vuxu.org>

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

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

https://github.com/ndowens/void-packages python-jsonschema
https://github.com/void-linux/void-packages/pull/26806

python3-jsonschema: update to 3.2.0
Add missing deps to packages that depends on python3-jsonschema; the simple method would have been to add python3-attrs and python3-pyrsistent to python3-jsonschema depends but decided not to do it this way. 

Tested anki, docker-compose, synapse and gns3-gui after changes and they launch fine. 
While testing, attaching fix for gns3-sever as upon launch gns3server gives certain version of aiohttp is needed @the-maldridge 

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

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

From 945af35d9b28c1d36192b6d055d57ad2c99e6a92 Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens@artixlinux.org>
Date: Sun, 29 Nov 2020 12:28:24 -0600
Subject: [PATCH 1/2] New package: python3-pyrsistent

---
 srcpkgs/python3-pyrsistent/template | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 srcpkgs/python3-pyrsistent/template

diff --git a/srcpkgs/python3-pyrsistent/template b/srcpkgs/python3-pyrsistent/template
new file mode 100644
index 00000000000..3dacb47944b
--- /dev/null
+++ b/srcpkgs/python3-pyrsistent/template
@@ -0,0 +1,20 @@
+# Template file for 'python3-pyrsistent'
+pkgname=python3-pyrsistent
+version=0.17.3
+revision=1
+wrksrc="pyrsistent-${version}"
+build_style=python3-module
+hostmakedepends="python3-setuptools"
+makedepends="python3-devel"
+depends="python3"
+checkdepends="python3-devel python3-hypothesis"
+short_desc="Python persistent immutable data structures"
+maintainer="Nathan Owens <ndowens@artixlinux.org>"
+license="MIT"
+homepage="https://github.com/tobgu/pyrsistent/"
+distfiles="${PYPI_SITE}/p/pyrsistent/pyrsistent-${version}.tar.gz"
+checksum=2e636185d9eb976a18a8a8e96efce62f2905fea90041958d8cc2a189756ebf3e
+
+post_install() {
+	vlicense LICENCE.mit LICENSE
+}

From 13a3cb2397f727fc029b1bc6c6a4cdc0e2c7b420 Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens@artixlinux.org>
Date: Sun, 29 Nov 2020 12:15:09 -0600
Subject: [PATCH 2/2] python3-jsonschema: update to 3.2.0

---
 srcpkgs/python3-jsonschema/template | 17 ++++++-----------
 1 file changed, 6 insertions(+), 11 deletions(-)

diff --git a/srcpkgs/python3-jsonschema/template b/srcpkgs/python3-jsonschema/template
index c3954b106dc..7757034dda7 100644
--- a/srcpkgs/python3-jsonschema/template
+++ b/srcpkgs/python3-jsonschema/template
@@ -1,27 +1,22 @@
 # Template file for 'python3-jsonschema'
 pkgname=python3-jsonschema
 reverts="3.0.2_1"
-version=2.6.0
-revision=6
+version=3.2.0
+revision=1
 wrksrc="jsonschema-${version}"
 build_style=python3-module
 hostmakedepends="python3-setuptools"
-depends="python3-setuptools"
+depends="python3-setuptools python3-six python3-attrs python3-pyrsistent"
+checkdepends="python3-pyrsistent python3-six python3-Twisted"
 short_desc="Implementation of JSON Schema for Python3"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
 homepage="https://github.com/Julian/jsonschema"
+changelog="https://raw.githubusercontent.com/Julian/jsonschema/master/CHANGELOG.rst"
 distfiles="${PYPI_SITE}/j/jsonschema/jsonschema-${version}.tar.gz"
-checksum=6ff5f3180870836cae40f06fa10419f557208175f13ad7bc26caa77beb1f6e02
+checksum=c8a85b28d377cc7737e46e2d9f2b4f44ee3c0e1deac6bf46ddefc7187d30797a
 conflicts="python-jsonschema>=0"
 
-pre_build() {
-	vsed -i setup.py \
-		-e '/setup_requires/d' \
-		-e '/vcversioner/d' \
-		-e "/name=/a\
-		version=\"${version}\","
-}
 post_install() {
 	vlicense COPYING LICENSE
 }

  parent reply	other threads:[~2020-12-17 20:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26806@inbox.vuxu.org>
2020-12-05 23:36 ` [PR REVIEW] " ericonr
2020-12-05 23:36 ` ericonr
2020-12-05 23:39 ` ndowens
2020-12-05 23:41 ` [PR PATCH] [Updated] " ndowens
2020-12-05 23:51 ` ericonr
2020-12-05 23:53 ` ndowens
2020-12-05 23:54 ` ndowens
2020-12-05 23:56 ` [PR PATCH] [Updated] " ndowens
2020-12-05 23:57 ` ndowens
2020-12-17  4:56 ` [PR REVIEW] " ericonr
2020-12-17  9:41 ` [PR PATCH] [Updated] " ndowens
2020-12-17 20:18 ` ericonr
2020-12-17 20:18 ` ericonr
2020-12-17 20:36 ` ndowens [this message]
2020-12-17 20:41 ` [PR PATCH] [Updated] " ndowens
2020-12-17 20:45 ` ndowens
2020-12-17 21:11 ` ericonr
2020-12-17 21:13 ` ndowens
2020-12-17 21:15 ` [PR PATCH] [Updated] " ndowens
2021-07-28  4:16 ` ericonr
2021-07-28  4:16 ` [PR PATCH] [Closed]: " 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=20201217203625.pjeYcQNK6juVlkASgNa5EcYC7PBgs-7w9AWWRL5ho6U@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).