From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [NOMERGE] libcap-ng: update to 0.8.1.
Date: Sat, 12 Dec 2020 15:39:22 +0100 [thread overview]
Message-ID: <20201212143922.TtaL-WETZYXOTu6abwxKyAOQ_XKf1rj35Cahe5WIpoY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26494@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
There is an updated pull request by ericonr against master on the void-packages repository
https://github.com/ericonr/void-packages caps
https://github.com/void-linux/void-packages/pull/26494
[NOMERGE] libcap-ng: update to 0.8.1.
Adds more error checking for some functions, which can lead to unexpected failures. I know about https://github.com/stevegrubb/libcap-ng/issues/21 , at the moment.
A patch file from https://github.com/void-linux/void-packages/pull/26494.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-caps-26494.patch --]
[-- Type: text/x-diff, Size: 1174 bytes --]
From 16fc251d3df7650630016121556556550641b3dd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89rico=20Rolim?= <erico.erc@gmail.com>
Date: Wed, 18 Nov 2020 19:42:08 -0300
Subject: [PATCH] libcap-ng: update to 0.8.2.
---
srcpkgs/libcap-ng/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/libcap-ng/template b/srcpkgs/libcap-ng/template
index 96f304d909a..99eab8e614f 100644
--- a/srcpkgs/libcap-ng/template
+++ b/srcpkgs/libcap-ng/template
@@ -1,7 +1,7 @@
# Template file for 'libcap-ng'
pkgname=libcap-ng
-version=0.8
-revision=2
+version=0.8.2
+revision=1
build_style=gnu-configure
configure_args="--without-python --without-python3"
short_desc="Alternate POSIX capabilities library"
@@ -9,7 +9,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later, LGPL-2.1-or-later"
homepage="http://people.redhat.com/sgrubb/libcap-ng/"
distfiles="http://people.redhat.com/sgrubb/$pkgname/$pkgname-$version.tar.gz"
-checksum=f14d23b60ae1465b032e4e8cbd4112006572c69a6017d55d5d3c6aad622a9e21
+checksum=52c083b77c2b0d8449dee141f9c3eba76e6d4c5ad44ef05df25891126cb85ae9
subpackages="libcap-ng-devel libcap-ng-progs"
next prev parent reply other threads:[~2020-12-12 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 22:45 [PR PATCH] " ericonr
2020-12-12 14:39 ` ericonr [this message]
2020-12-12 14:39 ` libcap-ng: update to 0.8.2 ericonr
2020-12-16 17:36 ` [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=20201212143922.TtaL-WETZYXOTu6abwxKyAOQ_XKf1rj35Cahe5WIpoY@z \
--to=ericonr@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).