public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 26/27] libcap: upgrade 2.47 -> 2.48
Date: Wed, 17 Feb 2021 13:52:09 +0800	[thread overview]
Message-ID: <20210217055210.22019-26-anuj.mittal@intel.com> (raw)
In-Reply-To: <20210217055210.22019-1-anuj.mittal@intel.com>

Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
 meta/recipes-support/libcap/{libcap_2.47.bb => libcap_2.48.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/libcap/{libcap_2.47.bb => libcap_2.48.bb} (96%)

diff --git a/meta/recipes-support/libcap/libcap_2.47.bb b/meta/recipes-support/libcap/libcap_2.48.bb
similarity index 96%
rename from meta/recipes-support/libcap/libcap_2.47.bb
rename to meta/recipes-support/libcap/libcap_2.48.bb
index bc4754eab8..d8bbebdde1 100644
--- a/meta/recipes-support/libcap/libcap_2.47.bb
+++ b/meta/recipes-support/libcap/libcap_2.48.bb
@@ -12,7 +12,7 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/libs/security/linux-privs/${BPN}2/${BPN}-${
            file://0002-tests-do-not-run-target-executables.patch \
            file://0001-tests-do-not-statically-link-a-test.patch \
            "
-SRC_URI[sha256sum] = "af165df45f9fe8b315164ec7143740947489f36ccbe6999b6cdf86e7a8dca04b"
+SRC_URI[sha256sum] = "4de9590ee09a87c282d558737ffb5b6175ccbfd26d580add10df44d0f047f6c2"
 
 UPSTREAM_CHECK_URI = "https://www.kernel.org/pub/linux/libs/security/linux-privs/${BPN}2/"
 
-- 
2.29.2


  parent reply	other threads:[~2021-02-17  5:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17  5:51 [PATCH 01/27] git: upgrade 2.30.0 -> 2.30.1 Anuj Mittal
2021-02-17  5:51 ` [PATCH 02/27] glib-2.0: upgrade 2.66.4 -> 2.66.7 Anuj Mittal
2021-02-17  5:51 ` [PATCH 03/27] help2man: upgrade 1.47.16 -> 1.48.1 Anuj Mittal
2021-02-17  5:51 ` [PATCH 04/27] libevdev: upgrade 1.10.1 -> 1.11.0 Anuj Mittal
2021-02-17  5:51 ` [PATCH 05/27] stress-ng: upgrade 0.12.02 -> 0.12.03 Anuj Mittal
2021-02-17  5:51 ` [PATCH 06/27] vte: upgrade 0.62.1 -> 0.62.2 Anuj Mittal
2021-02-17  5:51 ` [PATCH 07/27] x264: upgrade to latest revision Anuj Mittal
2021-02-17  5:51 ` [PATCH 08/27] createrepo-c: upgrade 0.16.2 -> 0.17.0 Anuj Mittal
2021-02-17  5:51 ` [PATCH 09/27] libuv: upgrade 1.40.0 -> 1.41.0 Anuj Mittal
2021-02-17  5:51 ` [PATCH 10/27] piglit: upgrade to latest revision Anuj Mittal
2021-02-17  5:51 ` [PATCH 11/27] pigz: upgrade 2.4 -> 2.6 Anuj Mittal
2021-02-17  5:51 ` [PATCH 12/27] python3-git: upgrade 3.1.12 -> 3.1.13 Anuj Mittal
2021-02-17  5:51 ` [PATCH 13/27] sysklogd: upgrade 2.1.2 -> 2.2.1 Anuj Mittal
2021-02-17  5:51 ` [PATCH 14/27] sysstat: upgrade 12.4.2 -> 12.4.3 Anuj Mittal
2021-02-17  5:51 ` [PATCH 15/27] python3-hypothesis: upgrade 6.0.2 -> 6.2.0 Anuj Mittal
2021-02-17  5:51 ` [PATCH 16/27] python3-jinja2: upgrade 2.11.2 -> 2.11.3 Anuj Mittal
2021-02-17  5:52 ` [PATCH 17/27] python3-more-itertools: upgrade 8.6.0 -> 8.7.0 Anuj Mittal
2021-02-17  5:52 ` [PATCH 18/27] python3-numpy: upgrade 1.20.0 -> 1.20.1 Anuj Mittal
2021-02-17  5:52 ` [PATCH 19/27] python3-pygments: upgrade 2.7.4 -> 2.8.0 Anuj Mittal
2021-02-17  5:52 ` [PATCH 20/27] python3-pytest: upgrade 6.2.1 -> 6.2.2 Anuj Mittal
2021-02-17  5:52 ` [PATCH 21/27] python3-setuptools: upgrade 52.0.0 -> 53.0.0 Anuj Mittal
2021-02-17  5:52 ` [PATCH 22/27] psmisc: upgrade 23.3 -> 23.4 Anuj Mittal
2021-02-17  5:52 ` [PATCH 23/27] gtk+3: upgrade 3.24.24 -> 3.24.25 Anuj Mittal
2021-02-17  5:52 ` [PATCH 24/27] lighttpd: upgrade 1.4.58 -> 1.4.59 Anuj Mittal
2021-02-17  5:52 ` [PATCH 25/27] libwebp: upgrade 1.1.0 -> 1.2.0 Anuj Mittal
2021-02-17  5:52 ` Anuj Mittal [this message]
2021-02-17  5:52 ` [PATCH 27/27] libxt: upgrade 1.2.0 -> 1.2.1 Anuj Mittal

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=20210217055210.22019-26-anuj.mittal@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=openembedded-core@lists.openembedded.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