Github messages for voidlinux
 help / color / mirror / Atom feed
From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libcap: update to 2.43.
Date: Fri, 21 Aug 2020 19:02:33 +0200	[thread overview]
Message-ID: <20200821170233.qBuGUuibLday1OfqpakKjI_oCI6YkYmNBj84OKjR_9A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24385@inbox.vuxu.org>

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

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

https://github.com/ailiop-git/void-packages libcap
https://github.com/void-linux/void-packages/pull/24385

libcap: update to 2.43.


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

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

From 132ae4ce32fd374b9ebfe65da0ac7103a56208d0 Mon Sep 17 00:00:00 2001
From: Anthony Iliopoulos <ailiop@altatus.com>
Date: Fri, 21 Aug 2020 19:02:00 +0200
Subject: [PATCH] libcap: update to 2.43.

---
 srcpkgs/libcap/template | 10 ++--------
 1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/srcpkgs/libcap/template b/srcpkgs/libcap/template
index 2e8a68b924e..952efce4c12 100644
--- a/srcpkgs/libcap/template
+++ b/srcpkgs/libcap/template
@@ -1,6 +1,6 @@
 # Template file for 'libcap'
 pkgname=libcap
-version=2.42
+version=2.43
 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=3605a9cb60076547ea9f64989e0ba576da9508e4653e8dc40ae54c0d6f443dfd
+checksum=512a0e5fc4c1e06d472a20da26aa96a9b9bf2a26b23f094f77f1b8da56cc427f
 
 if [ "$CHROOT_READY" ]; then
 	hostmakedepends="perl"
@@ -22,12 +22,6 @@ if [ "$CHROOT_READY" ]; then
 	fi
 fi
 
-pre_build() {
-	vsed -e 's,CC :=,CC ?=,' -i Make.Rules
-	# Disable tests, as they cause cross-build failure
-	vsed -e '/test:/,/.sh/d' -e '/tests/d' -i Makefile
-}
-
 libcap-devel_package() {
 	depends="libcap>=${version}_${revision}"
 	short_desc+=" - development files"

  reply	other threads:[~2020-08-21 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 15:41 [PR PATCH] " ailiop-git
2020-08-21 17:02 ` ailiop-git [this message]
2020-08-21 17:16 ` ailiop-git
2020-08-21 18:51 ` [PR PATCH] [Closed]: " ahesford

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=20200821170233.qBuGUuibLday1OfqpakKjI_oCI6YkYmNBj84OKjR_9A@z \
    --to=ailiop-git@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).