From: wangmy@fujitsu.com
To: openembedded-core@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] libidn2: upgrade 2.3.4 -> 2.3.7
Date: Thu, 1 Feb 2024 13:11:06 +0800 [thread overview]
Message-ID: <1706764266-12513-1-git-send-email-wangmy@fujitsu.com> (raw)
From: Wang Mingyu <wangmy@fujitsu.com>
Changelog:
===========
-Really include tests/standalone.sh in tarball.
-Bump libtool version numbers to reflect API/ABI addition.
-Include tests/standalone.sh in tarball.
License-Update: Copyright year updated to 2024.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../libidn/{libidn2_2.3.4.bb => libidn2_2.3.7.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-extended/libidn/{libidn2_2.3.4.bb => libidn2_2.3.7.bb} (83%)
diff --git a/meta/recipes-extended/libidn/libidn2_2.3.4.bb b/meta/recipes-extended/libidn/libidn2_2.3.7.bb
similarity index 83%
rename from meta/recipes-extended/libidn/libidn2_2.3.4.bb
rename to meta/recipes-extended/libidn/libidn2_2.3.7.bb
index b48de39fa0..7ae933e047 100644
--- a/meta/recipes-extended/libidn/libidn2_2.3.4.bb
+++ b/meta/recipes-extended/libidn/libidn2_2.3.7.bb
@@ -7,12 +7,12 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=2d834ea7d480438ada04e5d846152395 \
file://COPYING.LESSERv3;md5=e6a600fd5e1d9cbde2d983680233ad02 \
file://COPYINGv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
file://COPYING.unicode;md5=684cf5f7e3fded3546679424528261a9 \
- file://src/idn2.c;endline=16;md5=0f347a5b17acf44440bf53e406f1df70 \
- file://lib/idn2.h.in;endline=27;md5=4d7b3771faa9c60067ed1da914508bc5 \
+ file://src/idn2.c;endline=16;md5=afc1531bda991ba6338e33a7eff758a0 \
+ file://lib/idn2.h.in;endline=27;md5=f88d218005a5c45b68a83cecb5bd7f26 \
"
SRC_URI = "${GNU_MIRROR}/libidn/${BPN}-${PV}.tar.gz"
-SRC_URI[sha256sum] = "93caba72b4e051d1f8d4f5a076ab63c99b77faee019b72b9783b267986dbb45f"
+SRC_URI[sha256sum] = "4c21a791b610b9519b9d0e12b8097bf2f359b12f8dd92647611a929e6bfd7d64"
DEPENDS = "virtual/libiconv libunistring"
--
2.34.1
reply other threads:[~2024-02-01 5:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1706764266-12513-1-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.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