All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex.kanavin@gmail.com>
Subject: [PATCH 08/11] libgcrypt: upgrade 1.9.2 -> 1.9.3
Date: Fri,  4 Jun 2021 11:10:27 +0200	[thread overview]
Message-ID: <20210604091030.1380877-8-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20210604091030.1380877-1-alex.kanavin@gmail.com>

License-Update: added terms for cipher/cipher-gcm-ppc.c, still under GPL

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
 .../libgcrypt/{libgcrypt_1.9.2.bb => libgcrypt_1.9.3.bb}      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/libgcrypt/{libgcrypt_1.9.2.bb => libgcrypt_1.9.3.bb} (93%)

diff --git a/meta/recipes-support/libgcrypt/libgcrypt_1.9.2.bb b/meta/recipes-support/libgcrypt/libgcrypt_1.9.3.bb
similarity index 93%
rename from meta/recipes-support/libgcrypt/libgcrypt_1.9.2.bb
rename to meta/recipes-support/libgcrypt/libgcrypt_1.9.3.bb
index 34735ea5d7..fd3d8e09f2 100644
--- a/meta/recipes-support/libgcrypt/libgcrypt_1.9.2.bb
+++ b/meta/recipes-support/libgcrypt/libgcrypt_1.9.3.bb
@@ -14,7 +14,7 @@ LICENSE_dumpsexp-dev = "GPLv3+"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
                     file://COPYING.LIB;md5=bbb461211a33b134d42ed5ee802b37ff \
-                    file://LICENSES;md5=2dae15d91a37cfde72fe9eae75f8ea14 \
+                    file://LICENSES;md5=42fa35a25e138166cc40588387f9159d \
                     "
 
 DEPENDS = "libgpg-error"
@@ -27,7 +27,7 @@ SRC_URI = "${GNUPG_MIRROR}/libgcrypt/libgcrypt-${PV}.tar.bz2 \
            file://0004-tests-Makefile.am-fix-undefined-reference-to-pthread.patch \
            file://0001-Makefile.am-add-a-missing-space.patch \
            "
-SRC_URI[sha256sum] = "b2c10d091513b271e47177274607b1ffba3d95b188bbfa8797f948aec9053c5a"
+SRC_URI[sha256sum] = "97ebe4f94e2f7e35b752194ce15a0f3c66324e0ff6af26659bbfb5ff2ec328fd"
 
 # Below whitelisted CVEs are disputed and not affecting crypto libraries for any distro.
 CVE_CHECK_WHITELIST += "CVE-2018-12433 CVE-2018-12438"
-- 
2.31.1


  parent reply	other threads:[~2021-06-04  9:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04  9:10 [PATCH 01/11] virglrenderer: explicitly depend on libgbm Alexander Kanavin
2021-06-04  9:10 ` [PATCH 02/11] elfutils: update 0.183 -> 0.185 Alexander Kanavin
2021-06-04  9:10 ` [PATCH 03/11] libcap: update 2.49 -> 2.50 Alexander Kanavin
2021-06-04  9:10 ` [PATCH 04/11] cmake: update 3.20.2 -> 3.20.3 Alexander Kanavin
2021-06-04  9:10 ` [PATCH 05/11] perl: split perl-cross into its own recipe Alexander Kanavin
2021-06-17  9:22   ` [OE-core] " Yu, Mingli
2021-06-17  9:45     ` Alexander Kanavin
2021-06-04  9:10 ` [PATCH 06/11] perl-cross: 1.3.5 -> 1.3.6 Alexander Kanavin
2021-06-04  9:10 ` [PATCH 07/11] perl: update 5.32.1 -> 5.34.0 Alexander Kanavin
2021-06-04  9:10 ` Alexander Kanavin [this message]
2021-06-04  9:10 ` [PATCH 09/11] xf86-input-libinput: update 0.30.0 -> 1.0.1 Alexander Kanavin
2021-06-04  9:10 ` [PATCH 10/11] erofs-utils: correct upstream version check Alexander Kanavin
2021-06-04  9:10 ` [PATCH 11/11] perlcross fix Alexander Kanavin
2021-06-04  9:11   ` Alexander Kanavin

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=20210604091030.1380877-8-alex.kanavin@gmail.com \
    --to=alex.kanavin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.