Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package harfbuzz for openSUSE:Factory 
checked in at 2022-08-10 17:12:48
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/harfbuzz (Old)
 and      /work/SRC/openSUSE:Factory/.harfbuzz.new.1521 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "harfbuzz"

Wed Aug 10 17:12:48 2022 rev:92 rq:993935 version:5.1.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/harfbuzz/harfbuzz.changes        2022-07-05 
12:27:10.965844834 +0200
+++ /work/SRC/openSUSE:Factory/.harfbuzz.new.1521/harfbuzz.changes      
2022-08-10 17:13:04.389672467 +0200
@@ -1,0 +2,28 @@
+Wed Aug  3 07:45:27 UTC 2022 - Andreas Stieger <andreas.stie...@gmx.de>
+
+- harfbuzz 5.1.0:
+  + More extensive buffer tracing messages
+  + Fix hb-ft regression in bitmap fonts rendering
+  + Support extension promotion of lookups in hb-subset-repacker
+  + A new HB_GLYPH_FLAG_SAFE_TO_INSERT_TATWEEL for scripts that use
+    elongation (e.g. Arabic) to signify where it is safe to insert
+    tatweel glyph without interrupting shaping
+  + Add --safe-to-insert-tatweel to hb-shape tool
+- add harfbuzz-5.1.0-repacker-fix-signedness-of-char-in-tests.patch
+  from upstream to fix ARM and PPC builds
+
+-------------------------------------------------------------------
+Sun Jul 24 16:34:16 UTC 2022 - Andreas Stieger <andreas.stie...@gmx.de>
+
+- harfbuzz 5.0.1, including changes from 5.0.0:
+  + Improve for fonts with more than 65535 glyphs
+  + Support version 2 of ???avar??? table
+  + Improve support for some Arabic, Hebrew fonts
+  + Support for specific script tags to be retained in the 
+    subsetter, and add ???--layout-scripts??? option to ???hb-subset???
+    tool
+  + Improved handling of command line options
+  + Improve support for multiple tables and font features,
+    and font feature specific bug fixes
+
+-------------------------------------------------------------------

Old:
----
  harfbuzz-4.4.1.tar.xz

New:
----
  harfbuzz-5.1.0-repacker-fix-signedness-of-char-in-tests.patch
  harfbuzz-5.1.0.tar.xz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ harfbuzz.spec ++++++
--- /var/tmp/diff_new_pack.EXQpA7/_old  2022-08-10 17:13:05.613675662 +0200
+++ /var/tmp/diff_new_pack.EXQpA7/_new  2022-08-10 17:13:05.621675682 +0200
@@ -17,13 +17,14 @@
 
 
 Name:           harfbuzz
-Version:        4.4.1
+Version:        5.1.0
 Release:        0
 Summary:        An OpenType text shaping engine
 License:        MIT
 URL:            https://www.freedesktop.org/wiki/Software/HarfBuzz
 Source0:        
https://github.com/harfbuzz/harfbuzz/releases/download/%{version}/%{name}-%{version}.tar.xz
 Source99:       baselibs.conf
+Patch0:         harfbuzz-5.1.0-repacker-fix-signedness-of-char-in-tests.patch
 BuildRequires:  c++_compiler
 BuildRequires:  c_compiler
 BuildRequires:  meson

++++++ harfbuzz-5.1.0-repacker-fix-signedness-of-char-in-tests.patch ++++++
>From 04d28d94e576aab099891e6736fd0088dfac3366 Mon Sep 17 00:00:00 2001
From: psykose <al...@ayaya.dev>
Date: Mon, 1 Aug 2022 07:45:25 +0000
Subject: [PATCH] [repacker] fix signedness of char in tests

---
 src/test-repacker.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/test-repacker.cc b/src/test-repacker.cc
index 053c0c603..1b7e1f08b 100644
--- a/src/test-repacker.cc
+++ b/src/test-repacker.cc
@@ -112,9 +112,9 @@ static void start_lookup (int8_t type,
                           hb_serialize_context_t* c)
 {
   char lookup[] = {
-    0, type, // type
+    0, (char)type, // type
     0, 0, // flag
-    0, num_subtables, // num subtables
+    0, (char)num_subtables, // num subtables
   };
 
   start_object (lookup, 6, c);
-- 
2.37.1


++++++ harfbuzz-4.4.1.tar.xz -> harfbuzz-5.1.0.tar.xz ++++++
/work/SRC/openSUSE:Factory/harfbuzz/harfbuzz-4.4.1.tar.xz 
/work/SRC/openSUSE:Factory/.harfbuzz.new.1521/harfbuzz-5.1.0.tar.xz differ: 
char 26, line 1

Reply via email to