Github messages for voidlinux
 help / color / mirror / Atom feed
From: amak79 <amak79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libnpupnp: update to 5.0.1
Date: Fri, 26 May 2023 05:38:54 +0200	[thread overview]
Message-ID: <20230526033854.fuFv9X9rpJtneqkX2ToKYjgeWKUFt_ptAEM8xDOqzAk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42421@inbox.vuxu.org>

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

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

https://github.com/amak79/void-packages libnpupnp
https://github.com/void-linux/void-packages/pull/42421

libnpupnp: update to 5.0.1
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### 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, (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/42421.patch is attached

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

From b997db87c3235e03969892cf7fa9a3c1ec61c144 Mon Sep 17 00:00:00 2001
From: amak <amak.git@outlook.com>
Date: Fri, 24 Feb 2023 17:34:19 +1100
Subject: [PATCH] libnpupnp: update to 5.0.2

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

diff --git a/srcpkgs/libnpupnp/template b/srcpkgs/libnpupnp/template
index fc3b31046507..dc1496cfd692 100644
--- a/srcpkgs/libnpupnp/template
+++ b/srcpkgs/libnpupnp/template
@@ -1,6 +1,6 @@
 # Template file for 'libnpupnp'
 pkgname=libnpupnp
-version=5.0.0
+version=5.0.2
 revision=1
 build_style=gnu-configure
 hostmakedepends="pkg-config"
@@ -11,7 +11,7 @@ license="BSD-3-Clause"
 homepage="https://www.lesbonscomptes.com/upmpdcli/npupnp-doc/libnpupnp.html"
 changelog="https://www.lesbonscomptes.com/upmpdcli/pages/releases.html"
 distfiles="https://www.lesbonscomptes.com/upmpdcli/downloads/libnpupnp-${version}.tar.gz"
-checksum=2e5648cf180a425ef57b8c9c0d9dbd77f0314487ea0e0a85ebc6c3ef87cab05b
+checksum=33f90fc14906f2cea1bb7af56677b4e950eed6976e07d98a8e2b2e91b0755558
 
 post_install() {
 	vlicense COPYING

  parent reply	other threads:[~2023-05-26  3:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  6:35 [PR PATCH] " amak79
2023-05-26  1:53 ` github-actions
2023-05-26  3:38 ` amak79 [this message]
2023-05-26  9:02 ` [PR PATCH] [Merged]: libnpupnp: update to 5.0.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=20230526033854.fuFv9X9rpJtneqkX2ToKYjgeWKUFt_ptAEM8xDOqzAk@z \
    --to=amak79@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).