Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-jsonschema: update to 4.17.0.
Date: Mon, 14 Nov 2022 12:58:51 +0100	[thread overview]
Message-ID: <20221114115851.IsL6KHhuAkAxXI91TQyfdAu-lTvlGYgIPyE_hF-Lm4w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40337@inbox.vuxu.org>

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

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

https://github.com/jcgruenhage/void-packages python3-jsonschema-4.17.0_1
https://github.com/void-linux/void-packages/pull/40337

python3-jsonschema: update to 4.17.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/40337.patch is attached

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

From 41d054a2c68e84a215b118ebfb831105af785515 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Sat, 5 Nov 2022 12:31:24 +0100
Subject: [PATCH] python3-jsonschema: update to 4.17.0.

---
 srcpkgs/python3-jsonschema/template | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/python3-jsonschema/template b/srcpkgs/python3-jsonschema/template
index 2bd694599331..c458dfb7b282 100644
--- a/srcpkgs/python3-jsonschema/template
+++ b/srcpkgs/python3-jsonschema/template
@@ -1,22 +1,22 @@
 # Template file for 'python3-jsonschema'
 pkgname=python3-jsonschema
-version=4.16.0
-revision=2
+version=4.17.0
+revision=1
 build_style=python3-pep517
 hostmakedepends="hatchling hatch-vcs"
 depends="python3-attrs python3-pyrsistent"
-checkdepends="${depends} python3-pytest"
+checkdepends="${depends} python3-pytest python3-pip"
 short_desc="Implementation of JSON Schema for Python3"
 maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
 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=165059f076eff6971bae5b742fc029a7b4ef3f9bcf04c14e4776a7605de14b23
+checksum=5bfcf2bca16a087ade17e02b282d34af7ccd749ef76241e7f9bd7c0cb8a9424d
 
 do_check() {
 	rm -rf *.dist-info tmp # remove artifacts from previous unsuccessful check run
-	pip install --no-deps --target tmp ./jsonschema-$version-py3-none-any.whl
+	pip install --no-deps --target tmp ./dist/jsonschema-$version-py3-none-any.whl
 	rm tmp/jsonschema/tests -rf
 	mv tmp/*.dist-info .
 	PYTHONPATH=. pytest --deselect jsonschema/tests/test_jsonschema_test_suite.py::test_suite_bug

  reply	other threads:[~2022-11-14 11:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 11:32 [PR PATCH] " jcgruenhage
2022-11-14 11:58 ` jcgruenhage [this message]
2022-11-14 16:23 ` [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=20221114115851.IsL6KHhuAkAxXI91TQyfdAu-lTvlGYgIPyE_hF-Lm4w@z \
    --to=jcgruenhage@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).