From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libcap: Version bump. 2.66 -> 2.67.
Date: Fri, 10 Feb 2023 15:17:11 +0100 [thread overview]
Message-ID: <20230210141711.3533337-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230204173807.3333847-1-christian.melki@t2data.com>
Thanks, applied as 40ad4cef9646dd1c148326a89cd2fe9ccd7e72ec.
Michael
[sent from post-receive hook]
On Fri, 10 Feb 2023 15:17:11 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Minor bugfix release.
> https://sites.google.com/site/fullycapable/release-notes-for-libcap#h.o8papfkfh1x9
>
> * License hash changed. License file had SPDX identifiers added.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230204173807.3333847-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libcap.make b/rules/libcap.make
> index 8b4cf246bd13..496ef4b8d53f 100644
> --- a/rules/libcap.make
> +++ b/rules/libcap.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBCAP) += libcap
> #
> # Paths and names
> #
> -LIBCAP_VERSION := 2.66
> -LIBCAP_MD5 := 00afd6e13bc94b2543b1a70770bdb41f
> +LIBCAP_VERSION := 2.67
> +LIBCAP_MD5 := 06333f4301657298890fd8d6f1fb4793
> LIBCAP := libcap-$(LIBCAP_VERSION)
> LIBCAP_SUFFIX := tar.xz
> LIBCAP_URL := \
> @@ -23,7 +23,7 @@ LIBCAP_URL := \
> LIBCAP_SOURCE := $(SRCDIR)/$(LIBCAP).$(LIBCAP_SUFFIX)
> LIBCAP_DIR := $(BUILDDIR)/$(LIBCAP)
> LIBCAP_LICENSE := BSD-3-Clause OR GPL-2.0-only
> -LIBCAP_LICENSE_FILES := file://License;md5=e2370ba375efe9e1a095c26d37e483b8
> +LIBCAP_LICENSE_FILES := file://License;md5=2965a646645b72ecee859b43c592dcaa
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2023-02-10 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 17:38 [ptxdist] [PATCH] " Christian Melki
2023-02-10 14:17 ` 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=20230210141711.3533337-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