Github messages for voidlinux
 help / color / mirror / Atom feed
From: skmpz <skmpz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libcap: update to 2.45.
Date: Wed, 04 Nov 2020 18:16:25 +0100	[thread overview]
Message-ID: <20201104171625.SF4Lk8rX7uL1Si3qTpv0QDsb5WZ-qj5h-Yr1imN8R-8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26129@inbox.vuxu.org>

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

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

https://github.com/skmpz/void-packages libcap-2.45
https://github.com/void-linux/void-packages/pull/26129

libcap: update to 2.45.
Built for: 
- x86_64 [x86_64]
- i686 [i686]
- aarch64 [x86_64]
- armv7l [x86_64]
- x86_64-musl [x86_64-musl]
- aarch64-musl [x86_64-musl]
- armv6l-musl [x86_64-musl]

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

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

From 45452a9e4886950a8a9ed7385d88eb25ae3789f4 Mon Sep 17 00:00:00 2001
From: skmpz <dem.procopiou@gmail.com>
Date: Wed, 4 Nov 2020 21:10:09 +0400
Subject: [PATCH] libcap: update to 2.45.

---
 common/shlibs           | 1 +
 srcpkgs/libcap/template | 6 ++++--
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/common/shlibs b/common/shlibs
index 4270867b673..46dde74a4e2 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -202,6 +202,7 @@ libpam.so.0 pam-libs-1.1.6_3
 libpamc.so.0 pam-libs-1.1.6_3
 libpam_misc.so.0 pam-libs-1.1.6_3
 libcap.so.2 libcap-2.16_1
+libpsx.so.2 libcap-2.45_1
 liblzma.so.5 liblzma-5.0.0_1
 libuuid.so.1 libuuid-2.18_1
 libblkid.so.1 libblkid-2.18_1
diff --git a/srcpkgs/libcap/template b/srcpkgs/libcap/template
index 1cb8560b2b7..a8f99d7e6df 100644
--- a/srcpkgs/libcap/template
+++ b/srcpkgs/libcap/template
@@ -1,6 +1,6 @@
 # Template file for 'libcap'
 pkgname=libcap
-version=2.44
+version=2.45
 revision=1
 bootstrap=yes
 build_style=gnu-makefile
@@ -13,7 +13,7 @@ maintainer="skmpz <dem.procopiou@gmail.com>"
 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=92188359cd5be86e8e5bd3f6483ac6ce582264f912398937ef763def2205c8e1
+checksum=d66639f765c0e10557666b00f519caf0bd07a95f867dddaee131cd284fac3286
 
 if [ "$CROSS_BUILD" ]; then
 	make_build_args="CROSS_COMPILE=${XBPS_CROSS_TRIPLET}-"
@@ -33,6 +33,8 @@ libcap-devel_package() {
 		vmove usr/include
 		vmove usr/lib/libcap.a
 		vmove usr/lib/libcap.so
+		vmove usr/lib/libpsx.a
+		vmove usr/lib/libpsx.so
 		vmove usr/share/man/man3
 		vmove usr/lib/pkgconfig
 	}

  reply	other threads:[~2020-11-04 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 17:10 [PR PATCH] " skmpz
2020-11-04 17:16 ` skmpz [this message]
2020-11-06  2:29 ` [PR PATCH] [Merged]: " abenson

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=20201104171625.SF4Lk8rX7uL1Si3qTpv0QDsb5WZ-qj5h-Yr1imN8R-8@z \
    --to=skmpz@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).