Openembedded Core Discussions
 help / color / mirror / Atom feed
From: chee.yang.lee@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH][honister 1/4] harfbuzz: upgrade 2.9.0 -> 2.9.1
Date: Thu, 24 Feb 2022 14:28:53 +0800	[thread overview]
Message-ID: <20220224062856.2249762-1-chee.yang.lee@intel.com> (raw)

From: wangmy <wangmy@fujitsu.com>

Final subset API is in place and if no issues are discovered,
it will be the stable subset API of HarfBuzz 3.0.0.
Old API is kept to ease transition, but will be removed in 3.0.0.
Various fuzzer-found bug fixes.
hb_buffer_append() now handles the pre- and post-context which
previously were left unchanged in the destination buffer.
hb-view / hb-shape now accept following new arguments:
--unicodes-before/after: takes a list of hex numbers that represent Unicode
codepoints.
Undeprecated API:
hb_set_invert()

(From OE-Core rev: 0a9d19f575fda7db2f768f77701a137da8f73a97)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com>
---
 .../harfbuzz/{harfbuzz_2.9.0.bb => harfbuzz_2.9.1.bb}           | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/harfbuzz/{harfbuzz_2.9.0.bb => harfbuzz_2.9.1.bb} (95%)

diff --git a/meta/recipes-graphics/harfbuzz/harfbuzz_2.9.0.bb b/meta/recipes-graphics/harfbuzz/harfbuzz_2.9.1.bb
similarity index 95%
rename from meta/recipes-graphics/harfbuzz/harfbuzz_2.9.0.bb
rename to meta/recipes-graphics/harfbuzz/harfbuzz_2.9.1.bb
index bc91a8c03c..694553beef 100644
--- a/meta/recipes-graphics/harfbuzz/harfbuzz_2.9.0.bb
+++ b/meta/recipes-graphics/harfbuzz/harfbuzz_2.9.1.bb
@@ -12,7 +12,7 @@ UPSTREAM_CHECK_URI = "https://github.com/${BPN}/${BPN}/releases"
 UPSTREAM_CHECK_REGEX = "harfbuzz-(?P<pver>\d+(\.\d+)+).tar"
 
 SRC_URI = "https://github.com/${BPN}/${BPN}/releases/download/${PV}/${BPN}-${PV}.tar.xz"
-SRC_URI[sha256sum] = "3e1c2e1d2c65d56364fd16d1c41a06b2a35795496f78dfff635c2b7414b54c5a"
+SRC_URI[sha256sum] = "0edcc980f526a338452180e701d6aba6323aef457b6686976a7d17ccbddc51cf"
 
 inherit meson pkgconfig lib_package gtk-doc gobject-introspection
 
-- 
2.25.1



             reply	other threads:[~2022-02-24  6:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  6:28 chee.yang.lee [this message]
2022-02-24  6:28 ` [PATCH][honister 2/4] ruby: update 3.0.2 -> 3.0.3 chee.yang.lee
2022-02-24  6:28 ` [PATCH][honister 3/4] libarchive: upgrade 3.5.1 -> 3.5.2 chee.yang.lee
2022-02-24  6:28 ` [PATCH][honister 4/4] libarchive : update to 3.5.3 chee.yang.lee

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=20220224062856.2249762-1-chee.yang.lee@intel.com \
    --to=chee.yang.lee@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