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] libcap-ng: Version bump. 0.8.2 -> 0.8.3
Date: Mon,  4 Apr 2022 10:46:53 +0200	[thread overview]
Message-ID: <20220404084653.4102053-1-christian.melki@t2data.com> (raw)

Minor bugfixes and cleanups.
https://github.com/stevegrubb/libcap-ng/releases/tag/v0.8.3

Current certificate chain on the server people.redhat.com is
still broken. Reported to both Redhat and the developer.

The tarballs on github are not release tarballs in the
"make dist" sense. Just a repo archive.
So they dont hash the same as the release archive.

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

diff --git a/rules/libcap-ng.make b/rules/libcap-ng.make
index ccd650b79..530af64ef 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.2
-LIBCAP_NG_MD5		:= faf1ef766cf068ad1aba4008ced665f7
+LIBCAP_NG_VERSION	:= 0.8.3
+LIBCAP_NG_MD5		:= cdfc750af32f681293e43c5c1bd427c8
 LIBCAP_NG		:= libcap-ng-$(LIBCAP_NG_VERSION)
 LIBCAP_NG_SUFFIX	:= tar.gz
 LIBCAP_NG_URL		:= http://people.redhat.com/sgrubb/libcap-ng/$(LIBCAP_NG).$(LIBCAP_NG_SUFFIX)
-- 
2.32.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


             reply	other threads:[~2022-04-04  8:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  8:46 Christian Melki [this message]
2022-04-08 13:35 ` [ptxdist] [APPLIED] " 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=20220404084653.4102053-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