From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libcap-ng: Version bump. 0.9.5 -> 0.9.6
Date: Mon, 21 Sep 2026 08:38:17 +0200 [thread overview]
Message-ID: <20260921063817.3168291-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260912212233.2897839-1-christian.melki@t2data.com>
Thanks, applied as 246c1bae4ec5ca00d9a77b3e2b3a7662adbd561b.
Michael
[sent from post-receive hook]
On Mon, 21 Sep 2026 08:38:17 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Minor changes.
> https://github.com/stevegrubb/libcap-ng/releases/tag/v0.9.6
>
> * Forward patchset, applies cleanly.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260912212233.2897839-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/libcap-ng-0.9.5/0001-Makefile.am-Remove-bindings-dir.patch b/patches/libcap-ng-0.9.6/0001-Makefile.am-Remove-bindings-dir.patch
> similarity index 100%
> rename from patches/libcap-ng-0.9.5/0001-Makefile.am-Remove-bindings-dir.patch
> rename to patches/libcap-ng-0.9.6/0001-Makefile.am-Remove-bindings-dir.patch
> diff --git a/patches/libcap-ng-0.9.5/autogen.sh b/patches/libcap-ng-0.9.6/autogen.sh
> similarity index 100%
> rename from patches/libcap-ng-0.9.5/autogen.sh
> rename to patches/libcap-ng-0.9.6/autogen.sh
> diff --git a/patches/libcap-ng-0.9.5/series b/patches/libcap-ng-0.9.6/series
> similarity index 100%
> rename from patches/libcap-ng-0.9.5/series
> rename to patches/libcap-ng-0.9.6/series
> diff --git a/rules/libcap-ng.make b/rules/libcap-ng.make
> index 2762f643214b..f57da9172999 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.9.5
> -LIBCAP_NG_SHA256 := a2b4211f59b231d607c61ea2a13e9ecb38f446fe769b44e12da939d5af6d978a
> +LIBCAP_NG_VERSION := 0.9.6
> +LIBCAP_NG_SHA256 := 399040138e0ca62fa2bcabd63da9af4431a246ef7a654561a0ca3cb00010a539
> LIBCAP_NG := libcap-ng-$(LIBCAP_NG_VERSION)
> LIBCAP_NG_SUFFIX := tar.gz
> LIBCAP_NG_URL := \
prev parent reply other threads:[~2026-09-21 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 21:22 [ptxdist] [PATCH] " Christian Melki
2026-09-21 6:38 ` Michael Olbrich [this message]
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=20260921063817.3168291-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=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