mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 1/2] libcap-ng: Version bump. 0.8.3 -> 0.8.4
Date: Wed, 27 Dec 2023 19:57:44 +0100	[thread overview]
Message-ID: <20231227185745.2396946-1-christian.melki@t2data.com> (raw)

Minor changes.
https://github.com/stevegrubb/libcap-ng/compare/v0.8.3...v0.8.4

* Python2 support has been dropped, not that we used to create bindings,
but the option is removed, so drop it on our side too.

Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
 rules/libcap-ng.make | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/rules/libcap-ng.make b/rules/libcap-ng.make
index 64786e872..d8808877a 100644
--- a/rules/libcap-ng.make
+++ b/rules/libcap-ng.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBCAP_NG) += libcap-ng
 #
 # Paths and names
 #
-LIBCAP_NG_VERSION	:= 0.8.3
-LIBCAP_NG_MD5		:= cdfc750af32f681293e43c5c1bd427c8
+LIBCAP_NG_VERSION	:= 0.8.4
+LIBCAP_NG_MD5		:= 950748fcbc46a9bacf544e97724e46a2
 LIBCAP_NG		:= libcap-ng-$(LIBCAP_NG_VERSION)
 LIBCAP_NG_SUFFIX	:= tar.gz
 LIBCAP_NG_URL		:= \
@@ -41,7 +41,6 @@ LIBCAP_NG_CONF_OPT := \
 	$(CROSS_AUTOCONF_USR) \
 	--without-debug \
 	--without-warn \
-	--without-python \
 	--without-python3
 
 # ----------------------------------------------------------------------------
-- 
2.34.1




             reply	other threads:[~2023-12-27 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27 18:57 Christian Melki [this message]
2023-12-27 18:57 ` [ptxdist] [PATCH 2/2] host-libcap-ng: Follow suite from target libcap-ng Christian Melki
2024-01-10 16:57   ` [ptxdist] [APPLIED] " Michael Olbrich
2024-01-03 16:12 ` [ptxdist] [PATCH 1/2] libcap-ng: Version bump. 0.8.3 -> 0.8.4 Michael Olbrich

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=20231227185745.2396946-1-christian.melki@t2data.com \
    --to=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    /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