From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libcap: update to 2.29
Date: Fri, 27 Dec 2019 03:21:15 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17808@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
There is a new pull request by ndowens against master on the void-packages repository
https://github.com/ndowens/void-packages libcap
https://github.com/void-linux/void-packages/pull/17808
libcap: update to 2.29
A patch file from https://github.com/void-linux/void-packages/pull/17808.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libcap-17808.patch --]
[-- Type: text/x-diff, Size: 2089 bytes --]
From 2c6d61ac9241496f79c198ebcba9722819d36e00 Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens04@gmail.com>
Date: Thu, 26 Dec 2019 20:11:46 -0600
Subject: [PATCH 1/2] libcap: update to 2.29.
---
srcpkgs/libcap/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/libcap/template b/srcpkgs/libcap/template
index 877ed7136ec..d2cec1fa923 100644
--- a/srcpkgs/libcap/template
+++ b/srcpkgs/libcap/template
@@ -1,6 +1,6 @@
# Template file for 'libcap'
pkgname=libcap
-version=2.28
+version=2.29
revision=1
bootstrap=yes
build_style=gnu-makefile
@@ -13,7 +13,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-only"
homepage="http://sites.google.com/site/fullycapable/"
distfiles="${KERNEL_SITE}/libs/security/linux-privs/libcap2/${pkgname}-${version}.tar.xz"
-checksum=c0e70c3bcce288ada2bfe8d748e816b601590495312222e92e307cf18d6a38aa
+checksum=6c83352c316c40d1d4c8ad704e13dc36840ff05eccc36050aa18e42e7f2aa7f8
if [ "$CHROOT_READY" ]; then
hostmakedepends="perl"
From 51ce6cd7ac3a9f0f8ae19cf03756ea6780b99add Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens04@gmail.com>
Date: Thu, 26 Dec 2019 20:12:13 -0600
Subject: [PATCH 2/2] libcap-pam: update to 2.29.
---
srcpkgs/libcap-pam/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/libcap-pam/template b/srcpkgs/libcap-pam/template
index c6082caa511..8e65773666b 100644
--- a/srcpkgs/libcap-pam/template
+++ b/srcpkgs/libcap-pam/template
@@ -1,6 +1,6 @@
# Template file for 'libcap-pam'
pkgname=libcap-pam
-version=2.28
+version=2.29
revision=1
wrksrc="libcap-${version}"
build_style=gnu-makefile
@@ -13,7 +13,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-only"
homepage="http://sites.google.com/site/fullycapable/"
distfiles="${KERNEL_SITE}/libs/security/linux-privs/libcap2/libcap-${version}.tar.xz"
-checksum=c0e70c3bcce288ada2bfe8d748e816b601590495312222e92e307cf18d6a38aa
+checksum=6c83352c316c40d1d4c8ad704e13dc36840ff05eccc36050aa18e42e7f2aa7f8
conf_files="/etc/security/capability.conf"
next reply other threads:[~2019-12-27 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 2:21 voidlinux-github [this message]
2019-12-27 4:44 ` [PR PATCH] [Merged]: " voidlinux-github
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-17808@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).