Github messages for voidlinux
 help / color / mirror / Atom feed
From: dm1tz <dm1tz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-jsonschema: update to 4.2.1.
Date: Sun, 07 Nov 2021 00:17:14 +0100	[thread overview]
Message-ID: <20211106231714.91R23TaZMv-oImyFlC8BgCihu8zvHAG8jLznZP9liic@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33928@inbox.vuxu.org>

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

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

https://github.com/dm1tz/void-packages python3-jsonschema
https://github.com/void-linux/void-packages/pull/33928

python3-jsonschema: update to 4.2.1.
- Change build style to python3-pep517 because of Julian/jsonschema@112c809e.
- Remove python3-six dependency since py2 support was dropped in Julian/jsonschema@027feac.

<!-- 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?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] 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
-->


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

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

From d9dc024ead8af0957c973b29d226ce3f00382416 Mon Sep 17 00:00:00 2001
From: Dmitry Zakharchenko <dmitriyz447@gmail.com>
Date: Sat, 6 Nov 2021 18:58:02 +0200
Subject: [PATCH] python3-jsonschema: update to 4.2.1.

- Change build style to python3-pep517 because of Julian/jsonschema@112c809e.
- Remove python3-six dependency since py2 support was dropped
in Julian/jsonschema@027feac.
- Add pip and wheel to checkdepends since some tests require package itself.
---
 srcpkgs/python3-jsonschema/template | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/srcpkgs/python3-jsonschema/template b/srcpkgs/python3-jsonschema/template
index 3b365347c22e..78e33b188949 100644
--- a/srcpkgs/python3-jsonschema/template
+++ b/srcpkgs/python3-jsonschema/template
@@ -1,19 +1,19 @@
 # Template file for 'python3-jsonschema'
 pkgname=python3-jsonschema
-version=3.2.0
-revision=2
+version=4.2.1
+revision=1
 wrksrc="jsonschema-${version}"
-build_style=python3-module
-hostmakedepends="python3-setuptools_scm"
-depends="python3-setuptools python3-six python3-attrs python3-pyrsistent"
-checkdepends="python3-pytest python3-Twisted $depends"
+build_style=python3-pep517
+hostmakedepends="python3-setuptools_scm python3-wheel"
+depends="python3-setuptools python3-attrs python3-pyrsistent"
+checkdepends="python3-pip python3-wheel $depends"
 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=c8a85b28d377cc7737e46e2d9f2b4f44ee3c0e1deac6bf46ddefc7187d30797a
+checksum=390713469ae64b8a58698bb3cbc3859abe6925b565a973f87323ef21b09a27a8
 
 post_install() {
 	vlicense COPYING LICENSE

  parent reply	other threads:[~2021-11-06 23:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-06 17:19 [PR PATCH] " dm1tz
2021-11-06 17:28 ` [PR PATCH] [Updated] " dm1tz
2021-11-06 23:17 ` dm1tz [this message]
2021-11-06 23:21 ` Chocimier
2021-11-07  0:16 ` [PR PATCH] [Updated] " dm1tz
2021-11-07  0:19 ` dm1tz
2021-11-07  0:32 ` dm1tz
2021-11-07  1:05 ` [PR PATCH] [Updated] " dm1tz
2021-11-07  1:06 ` dm1tz
2021-11-07 10:37 ` [PR REVIEW] " paper42
2021-11-07 11:14 ` [PR PATCH] [Updated] " dm1tz
2021-11-07 11:16 ` dm1tz
2021-11-07 11:18 ` [PR REVIEW] " dm1tz
2021-11-07 12:27 ` paper42
2021-11-07 14:44 ` dm1tz
2021-11-07 15:40 ` paper42
2021-11-08  3:02 ` tsndqst
2021-11-08 15:46 ` dm1tz
2021-11-08 15:48 ` dm1tz
2021-11-11  0:11 ` tsndqst
2021-11-11 14:38 ` TinfoilSubmarine
2021-11-13 19:42 ` [PR PATCH] [Merged]: " paper42

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=20211106231714.91R23TaZMv-oImyFlC8BgCihu8zvHAG8jLznZP9liic@z \
    --to=dm1tz@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).