Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/6] harfbuzz: upgrade 14.5.1 -> 14.6.0
Date: Wed,  7 Oct 2026 07:58:16 +0200	[thread overview]
Message-ID: <20261007055820.59633-2-jaipaul.cheernam@est.tech> (raw)
In-Reply-To: <20261007055820.59633-1-jaipaul.cheernam@est.tech>

Overview of changes leading to 14.6.0
Monday, October 5, 2026
=====================================
- Fix shaping failures caused by out-of-range glyph IDs, a regression from
  11.4.0.
- Update experimental beyond-64k support to the final ISO Open Font Format
  5th edition. This support remains disabled by default.
- Add support for the `DMAP` table.
- Support `FeatureVariations` 1.1 lookup variations, including subsetting and
  instancing.
- Update `VARC` to the revised variation-store format. The new format is
  incompatible with the previous one.
- Various `VARC` fixes.
- Fix background color and stride handling in the experimental raster library.
- Improve the experimental Rust shaper (HarfRust) and font functions
  (`fontations`), and update HarfRust to 0.14.
- Various subsetting fixes and improvements.
- Various fixes for malformed fonts.
- Various build and CI fixes.

Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
---
 .../harfbuzz/{harfbuzz_14.5.1.bb => harfbuzz_14.6.0.bb}         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/harfbuzz/{harfbuzz_14.5.1.bb => harfbuzz_14.6.0.bb} (96%)

diff --git a/meta/recipes-graphics/harfbuzz/harfbuzz_14.5.1.bb b/meta/recipes-graphics/harfbuzz/harfbuzz_14.6.0.bb
similarity index 96%
rename from meta/recipes-graphics/harfbuzz/harfbuzz_14.5.1.bb
rename to meta/recipes-graphics/harfbuzz/harfbuzz_14.6.0.bb
index d10f1bfa01..7ef0897a18 100644
--- a/meta/recipes-graphics/harfbuzz/harfbuzz_14.5.1.bb
+++ b/meta/recipes-graphics/harfbuzz/harfbuzz_14.6.0.bb
@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b98429b8e8e3c2a67cfef01e99e4893d \
                     "
 
 SRC_URI = "${GITHUB_BASE_URI}/download/${PV}/${BPN}-${PV}.tar.xz"
-SRC_URI[sha256sum] = "7e2fa4e8c7c98e8d8140671f5772542afaaa6acccfbd746506886b6d85f7f8d6"
+SRC_URI[sha256sum] = "d07a007327277708a2a73ae437887cdbaf282937f6d03ca5467723e9099af586"
 
 inherit meson pkgconfig lib_package gtk-doc gobject-introspection github-releases
 


  reply	other threads:[~2026-10-07  5:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07  5:58 [PATCH 1/6] cups: upgrade 2.4.19 -> 2.4.20 Jaipaul Cheernam
2026-10-07  5:58 ` Jaipaul Cheernam [this message]
2026-10-07  5:58 ` [PATCH 3/6] rpm-sequoia-crypto-policy: upgrade to latest revision Jaipaul Cheernam
2026-10-07  5:58 ` [PATCH 4/6] python3-hypothesis: upgrade 6.168.3 -> 6.168.5 Jaipaul Cheernam
2026-10-07  5:58 ` [PATCH 5/6] python3-more-itertools: upgrade 10.8.0 -> 11.1.0 Jaipaul Cheernam
2026-10-07 14:23   ` [OE-core] " Mathieu Dubois-Briand
2026-10-08  7:21     ` Trevor Gamblin
2026-10-08 18:21   ` [PATCH v2] " Jaipaul Cheernam
2026-10-12 17:10     ` [OE-core] " Alexander Kanavin
2026-10-14 17:53       ` Jaipaul Cheernam
2026-10-07  5:58 ` [PATCH 6/6] python3-rpds-py: upgrade 2026.6.3 -> 2026.9.1 Jaipaul Cheernam

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=20261007055820.59633-2-jaipaul.cheernam@est.tech \
    --to=jaipaul.cheernam@est.tech \
    --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