Github messages for voidlinux
 help / color / mirror / Atom feed
From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] gping: update to 1.3.1
Date: Thu, 16 Jun 2022 18:02:35 +0200	[thread overview]
Message-ID: <20220616160235.6kbxRdpke0U3kxZZUUPqm9T2KU0CX3ZM72SCvRJQCdY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37541@inbox.vuxu.org>

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

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

https://github.com/cinerea0/void-packages gping
https://github.com/void-linux/void-packages/pull/37541

gping: update to 1.3.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 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/37541.patch is attached

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

From d74b6fbe71c5f1d51de2c2ce5890244c09ea780c Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Thu, 16 Jun 2022 12:02:17 -0400
Subject: [PATCH] gping: update to 1.3.2

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

diff --git a/srcpkgs/gping/template b/srcpkgs/gping/template
index c3fb77d05345..b5f3c94a3487 100644
--- a/srcpkgs/gping/template
+++ b/srcpkgs/gping/template
@@ -1,6 +1,6 @@
 # Template file for 'gping'
 pkgname=gping
-version=1.2.6
+version=1.3.2
 revision=1
 wrksrc="${pkgname}-${pkgname}-v${version}"
 build_wrksrc="gping"
@@ -10,7 +10,7 @@ maintainer="Paper <paper@tilde.institute>"
 license="MIT"
 homepage="https://github.com/orf/gping/"
 distfiles="https://github.com/orf/gping/archive/refs/tags/gping-v${version}.tar.gz"
-checksum=e36d5bc02157708c803d1855be4b2a9daa27d077fffe86c58b12c746fdc04c8f
+checksum=1ab71ca45cb5da317d77774eff96d5868486d03ea1cedff008cbafcaf880332b
 
 post_install() {
 	vlicense ../LICENSE

  reply	other threads:[~2022-06-16 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13  1:25 [PR PATCH] " cinerea0
2022-06-16 16:02 ` cinerea0 [this message]
2022-06-19  2:01 ` [PR PATCH] [Merged]: gping: update to 1.3.2 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=20220616160235.6kbxRdpke0U3kxZZUUPqm9T2KU0CX3ZM72SCvRJQCdY@z \
    --to=cinerea0@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).