Github messages for voidlinux
 help / color / mirror / Atom feed
From: wpbirney <wpbirney@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] forkstat: update to 0.03.02
Date: Wed, 03 Apr 2024 05:04:52 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49690@inbox.vuxu.org> (raw)

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

There is a new pull request by wpbirney against master on the void-packages repository

https://github.com/wpbirney/void-packages forkstat-0.03.02
https://github.com/void-linux/void-packages/pull/49690

forkstat: update to 0.03.02
<!-- 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 [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, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl (cross)
  - x86_64-musl

A patch file from https://github.com/void-linux/void-packages/pull/49690.patch is attached

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

From efdb46837265e92437ecb69ab35fd7e97314f69d Mon Sep 17 00:00:00 2001
From: wpbirney <wpb@360scada.com>
Date: Tue, 2 Apr 2024 23:02:17 -0400
Subject: [PATCH] forkstat: update to 0.03.02

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

diff --git a/srcpkgs/forkstat/template b/srcpkgs/forkstat/template
index f11c1aac6e52c4..bdef3ea1722938 100644
--- a/srcpkgs/forkstat/template
+++ b/srcpkgs/forkstat/template
@@ -1,6 +1,6 @@
 # Template file for 'forkstat'
 pkgname=forkstat
-version=0.03.01
+version=0.03.02
 revision=1
 build_style=gnu-makefile
 make_use_env=yes
@@ -10,4 +10,4 @@ license="GPL-2.0-or-later"
 homepage="https://github.com/ColinIanKing/forkstat"
 changelog="https://github.com/ColinIanKing/forkstat/raw/master/debian/changelog"
 distfiles="${DEBIAN_SITE}/main/f/forkstat/forkstat_${version}.orig.tar.xz"
-checksum=26c323c2a2da18bdc4a9ed80454105958434b35a199cd40b464ec66c94e95743
+checksum=571e7c50703b2eac8d1c5476e5edf24dd2f5c7beff4e3719f090efd376ab950d

             reply	other threads:[~2024-04-03  3:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  3:04 wpbirney [this message]
2024-04-03 14:17 ` [PR PATCH] [Merged]: " cinerea0

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-49690@inbox.vuxu.org \
    --to=wpbirney@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).