Github messages for voidlinux
 help / color / mirror / Atom feed
From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] yq-go: update to 4.20.1.
Date: Sun, 20 Feb 2022 12:26:26 +0100	[thread overview]
Message-ID: <20220220112626.FWrto6iYd0ehP7GFChbMK_zABPB4Bb4m9LoPtD2bgXY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35677@inbox.vuxu.org>

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

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

https://github.com/steinex/void-packages yq-go
https://github.com/void-linux/void-packages/pull/35677

yq-go: update to 4.20.1.
<!-- 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 [skip CI](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/35677.patch is attached

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

From 308c2a7678b70e675a785722160cee5e85972100 Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Fri, 18 Feb 2022 10:39:08 +0100
Subject: [PATCH] yq-go: update to 4.20.2.

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

diff --git a/srcpkgs/yq-go/template b/srcpkgs/yq-go/template
index a69c6ddb26bd..1a2e1ee53dab 100644
--- a/srcpkgs/yq-go/template
+++ b/srcpkgs/yq-go/template
@@ -1,6 +1,6 @@
 # Template file for 'yq-go'
 pkgname=yq-go
-version=4.19.1
+version=4.20.2
 revision=1
 wrksrc="yq-${version}"
 build_style=go
@@ -9,8 +9,9 @@ short_desc="Lightweight and portable command-line YAML processor written in go"
 maintainer="Frank Steinborn <steinex@nognu.de>"
 license="MIT"
 homepage="https://github.com/mikefarah/yq"
+changelog="https://raw.githubusercontent.com/mikefarah/yq/master/release_notes.txt"
 distfiles="https://github.com/mikefarah/yq/archive/v${version}.tar.gz"
-checksum=c289cef82668722d1851fd4e70fd7bbfdbf5b6fd358d7bb01a9e06c317dafc58
+checksum=031c63dd98e564b9a74b842ffe8ae929085f1486f59a27d4feb7e118f40c8a1e
 
 do_check() {
 	go test -v

  parent reply	other threads:[~2022-02-20 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  9:47 [PR PATCH] " steinex
2022-02-19 23:56 ` [PR REVIEW] " paper42
2022-02-20 11:26 ` steinex [this message]
2022-02-20 12:04 ` [PR PATCH] [Merged]: yq-go: update to 4.20.2 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=20220220112626.FWrto6iYd0ehP7GFChbMK_zABPB4Bb4m9LoPtD2bgXY@z \
    --to=steinex@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).