From: knusbaum <knusbaum@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nmon: update to 16n.
Date: Thu, 06 Jan 2022 01:44:52 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34885@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
There is a new pull request by knusbaum against master on the void-packages repository
https://github.com/knusbaum/void-packages UPDATE-nmon-16n
https://github.com/void-linux/void-packages/pull/34885
nmon: update to 16n.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/34885.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-UPDATE-nmon-16n-34885.patch --]
[-- Type: text/x-diff, Size: 1604 bytes --]
From 40c25b364482f1903d474e060c661ef7ce6cf62d Mon Sep 17 00:00:00 2001
From: Kyle Nusbaum <KyleJNusbaum@gmail.com>
Date: Wed, 5 Jan 2022 18:42:29 +0000
Subject: [PATCH] nmon: update to 16n.
---
srcpkgs/nmon/patches/musl-fixes.patch | 4 ++--
srcpkgs/nmon/template | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/nmon/patches/musl-fixes.patch b/srcpkgs/nmon/patches/musl-fixes.patch
index a9da244e9cec..be819684c6a0 100644
--- a/srcpkgs/nmon/patches/musl-fixes.patch
+++ b/srcpkgs/nmon/patches/musl-fixes.patch
@@ -1,5 +1,5 @@
---- a/lmon16m.c 2019-04-19 14:59:07.091281022 -0500
-+++ b/lmon16m.c 2019-04-19 15:01:58.550285273 -0500
+--- a/lmon16n.c 2019-04-19 14:59:07.091281022 -0500
++++ b/lmon16n.c 2019-04-19 15:01:58.550285273 -0500
@@ -61,7 +61,7 @@
#include <fcntl.h>
#include <math.h>
diff --git a/srcpkgs/nmon/template b/srcpkgs/nmon/template
index 76f09917adea..790ed6d8d5c9 100644
--- a/srcpkgs/nmon/template
+++ b/srcpkgs/nmon/template
@@ -1,7 +1,7 @@
# Template file for 'nmon'
pkgname=nmon
-version=16m
-revision=2
+version=16n
+revision=1
build_style=fetch
makedepends="ncurses-devel"
depends="ncurses"
@@ -10,7 +10,7 @@ maintainer="Kyle Nusbaum <knusbaum+void@sdf.org>"
license="GPL-3.0-or-later"
homepage="http://nmon.sourceforge.net/pmwiki.php?n=Main.HomePage"
distfiles="${SOURCEFORGE_SITE}/nmon/files/lmon${version}.c"
-checksum=2bed4d45fdfdf1d1387ec91e139c04975d5f838e3e0d53c0fe2d803a707e5fc1
+checksum=c0012cc2d925dee940c37ceae297abac64ba5a5c30e575e7418b04028613f5f2
do_build() {
case "$XBPS_TARGET_MACHINE" in
next reply other threads:[~2022-01-06 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 0:44 knusbaum [this message]
2022-01-06 1:58 ` [PR PATCH] [Merged]: " ericonr
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-34885@inbox.vuxu.org \
--to=knusbaum@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).