From: RunningDroid <RunningDroid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-jq: update to 1.4.1
Date: Fri, 17 Mar 2023 09:10:21 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42819@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
There is a new pull request by RunningDroid against master on the void-packages repository
https://github.com/RunningDroid/void-packages update_python3-jq
https://github.com/void-linux/void-packages/pull/42819
python3-jq: update to 1.4.1
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### 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/42819.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update_python3-jq-42819.patch --]
[-- Type: text/x-diff, Size: 1109 bytes --]
From 83741300a349e940453afcf2e03484f180156c02 Mon Sep 17 00:00:00 2001
From: RunningDroid <runningdroid@zoho.com>
Date: Fri, 17 Mar 2023 04:07:09 -0400
Subject: [PATCH] python3-jq: update to 1.4.1
---
srcpkgs/python3-jq/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-jq/template b/srcpkgs/python3-jq/template
index 1f2b10f0dea5..96a87c6f8603 100644
--- a/srcpkgs/python3-jq/template
+++ b/srcpkgs/python3-jq/template
@@ -1,6 +1,6 @@
# Template file for 'python3-jq'
pkgname=python3-jq
-version=1.4.0
+version=1.4.1
revision=1
build_style=python3-module
hostmakedepends="python3-setuptools python3-Cython"
@@ -12,7 +12,7 @@ license="BSD-2-Clause"
homepage="https://pypi.org/project/jq/"
changelog="https://raw.githubusercontent.com/mwilliamson/jq.py/master/CHANGELOG.rst"
distfiles="https://github.com/mwilliamson/jq.py/archive/${version}.tar.gz"
-checksum=b894642f13e9a6d8ccbde24d21e03003c4b873a48ad68809bb390e0262e40dc4
+checksum=24239bd49a01a91ee313bf805c3bc7eb0ecfd71ca1bd4b94a73bd00585d79349
pre_build() {
cython -X language_level=3 jq.pyx
next reply other threads:[~2023-03-17 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 8:10 RunningDroid [this message]
2023-03-18 6:28 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42819@inbox.vuxu.org \
--to=runningdroid@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).