From: Heiko Stuebner <heiko@sntech.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] package/icu: bump to version 68-1
Date: Thu, 17 Dec 2020 18:23:22 +0100 [thread overview]
Message-ID: <20201217172322.3561127-1-heiko@sntech.de> (raw)
From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
Bump icu to the newest release.
Tested in conjunction with qt 5.15.1 and a qt-based application.
Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
---
changes in v3:
- fix license hash in new version
changes in v2:
- redo commit message
- drop the mention of the CVE, that was already fixed in 67.1
package/icu/icu.hash | 4 ++--
package/icu/icu.mk | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/icu/icu.hash b/package/icu/icu.hash
index 5c10008d8a..80cdd7df0c 100644
--- a/package/icu/icu.hash
+++ b/package/icu/icu.hash
@@ -1,3 +1,3 @@
# Locally computed
-sha256 94a80cd6f251a53bd2a997f6f1b5ac6653fe791dfab66e1eb0227740fb86d5dc icu4c-67_1-src.tgz
-sha256 25e21013a7bc2fad735e28c5278a120e4c7f1c327c8c8b9b4df1751748cddbb2 LICENSE
+sha256 a9f2e3d8b4434b8e53878b4308bd1e6ee51c9c7042e2b1a376abefb6fbb29f2d icu4c-68_1-src.tgz
+sha256 7915b19db903070778581ae05d8bf4ea241b34a05deb51ca4f5cbb15ea1cbba3 LICENSE
diff --git a/package/icu/icu.mk b/package/icu/icu.mk
index c07ca2da3b..8d0288578c 100644
--- a/package/icu/icu.mk
+++ b/package/icu/icu.mk
@@ -7,7 +7,7 @@
# Git tags (and therefore versions on release-monitoring.org) use the
# XX-Y format, but the tarballs are named XX_Y and the containing
# directories XX.Y.
-ICU_VERSION = 67-1
+ICU_VERSION = 68-1
ICU_SOURCE = icu4c-$(subst -,_,$(ICU_VERSION))-src.tgz
ICU_SITE = \
https://github.com/unicode-org/icu/releases/download/release-$(ICU_VERSION)
--
2.29.2
next reply other threads:[~2020-12-17 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 17:23 Heiko Stuebner [this message]
2020-12-31 14:27 ` [Buildroot] [PATCH v3] package/icu: bump to version 68-1 Thomas Petazzoni
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=20201217172322.3561127-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=buildroot@busybox.net \
/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.