From: ishaanbhimwal <ishaanbhimwal@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] yq: update to 3.0.2
Date: Wed, 20 Jul 2022 22:28:03 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38158@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
There is a new pull request by ishaanbhimwal against master on the void-packages repository
https://github.com/ishaanbhimwal/void-packages yq
https://github.com/void-linux/void-packages/pull/38158
yq: update to 3.0.2
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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/38158.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-yq-38158.patch --]
[-- Type: text/x-diff, Size: 1138 bytes --]
From c0e660869dd28a040fee0f929b8bc31ff93340f3 Mon Sep 17 00:00:00 2001
From: Ishaan Bhimwal <ishaanbhimwal@protonmail.com>
Date: Thu, 21 Jul 2022 01:56:12 +0530
Subject: [PATCH] yq: update to 3.0.2
---
srcpkgs/yq/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/yq/template b/srcpkgs/yq/template
index b775674672ac..ff622cb65b50 100644
--- a/srcpkgs/yq/template
+++ b/srcpkgs/yq/template
@@ -1,6 +1,6 @@
# Template file for 'yq'
pkgname=yq
-version=3.0.1
+version=3.0.2
revision=1
build_style=python3-module
hostmakedepends="python3-setuptools_scm"
@@ -11,8 +11,9 @@ short_desc="Command-line YAML processor written in Python that wraps around jq"
maintainer="Ishaan Bhimwal <ishaanbhimwal@protonmail.com>"
license="Apache-2.0"
homepage="https://github.com/kislyuk/yq"
+changelog="https://raw.githubusercontent.com/kislyuk/yq/develop/Changes.rst"
distfiles="${PYPI_SITE}/y/yq/yq-${version}.tar.gz"
-checksum=a5e61078facd7ee4222f4346b5b50c4e9cea5e9d3330f074b5ea2c203bf639b1
+checksum=e47ff2479a3746f90bdbb77f84e3ebdb789ce46a092b1c261ae5b1f5f914f8e8
do_check() {
python3 test/test.py
next reply other threads:[~2022-07-20 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 20:28 ishaanbhimwal [this message]
2022-07-21 3:21 ` [PR PATCH] [Merged]: " classabbyamp
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-38158@inbox.vuxu.org \
--to=ishaanbhimwal@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).