Github messages for voidlinux
 help / color / mirror / Atom feed
From: ishaanbhimwal <ishaanbhimwal@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] yq: update to 3.1.0
Date: Tue, 26 Jul 2022 20:40:36 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38285@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/38285

yq: update to 3.1.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 [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/38285.patch is attached

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

From d279f84c71a1c310f391dd57462bb84e952fb7b8 Mon Sep 17 00:00:00 2001
From: Ishaan Bhimwal <ishaanbhimwal@protonmail.com>
Date: Wed, 27 Jul 2022 00:08:40 +0530
Subject: [PATCH] yq: update to 3.1.0

---
 srcpkgs/yq/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/yq/template b/srcpkgs/yq/template
index ff622cb65b50..20affe54bc63 100644
--- a/srcpkgs/yq/template
+++ b/srcpkgs/yq/template
@@ -1,6 +1,6 @@
 # Template file for 'yq'
 pkgname=yq
-version=3.0.2
+version=3.1.0
 revision=1
 build_style=python3-module
 hostmakedepends="python3-setuptools_scm"
@@ -13,7 +13,7 @@ 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=e47ff2479a3746f90bdbb77f84e3ebdb789ce46a092b1c261ae5b1f5f914f8e8
+checksum=30a84aa22486c749ba269256bd586c0bcd370b7e2a71e76c3924ead4867e74f2
 
 do_check() {
 	python3 test/test.py

             reply	other threads:[~2022-07-26 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 18:40 ishaanbhimwal [this message]
2022-07-26 19:09 ` [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-38285@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).