Created attachment 231473 [details] v1 Moin moin desktop@ would like to ask for an exp-run to update print/harfbuzz* to 3.3.0 The patch is attached, and can also be found here: https://people.freebsd.org/~tcberner/patches/0001-print-harfbuzz-update-to-3.3.0.patch mfg Tobias
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=d3b163b46be94e1317d1ee52ca44058c65a99843 commit d3b163b46be94e1317d1ee52ca44058c65a99843 Author: Jan Beich <jbeich@FreeBSD.org> AuthorDate: 2022-01-31 16:40:10 +0000 Commit: Jan Beich <jbeich@FreeBSD.org> CommitDate: 2022-01-31 22:50:46 +0000 print/harfbuzz: update to 3.3.1 Changes: https://github.com/harfbuzz/harfbuzz/releases/tag/3.3.0 Changes: https://github.com/harfbuzz/harfbuzz/releases/tag/3.3.1 PR: 261605 Reported by: GitHub (watch releases) print/harfbuzz/Makefile | 4 ++-- print/harfbuzz/distinfo | 6 +++--- print/harfbuzz/pkg-plist | 1 + 3 files changed, 6 insertions(+), 5 deletions(-)
harfbuzz updates are not risky. Only 3.0.0 caused minor regressions: only few consumers broke but those were popular. Besides, already obsoleted by https://github.com/harfbuzz/harfbuzz/releases/tag/3.3.1
A commit in branch 2022Q1 references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=2d3224c4705d8913d28042ebc422912c636bcb9d commit 2d3224c4705d8913d28042ebc422912c636bcb9d Author: Jan Beich <jbeich@FreeBSD.org> AuthorDate: 2022-01-31 16:40:10 +0000 Commit: Jan Beich <jbeich@FreeBSD.org> CommitDate: 2022-03-31 18:31:57 +0000 print/harfbuzz: update to 3.3.1 Changes: https://github.com/harfbuzz/harfbuzz/releases/tag/3.3.0 Changes: https://github.com/harfbuzz/harfbuzz/releases/tag/3.3.1 PR: 261605 Reported by: GitHub (watch releases) (cherry picked from commit d3b163b46be94e1317d1ee52ca44058c65a99843) print/harfbuzz/Makefile | 4 ++-- print/harfbuzz/distinfo | 6 +++--- print/harfbuzz/pkg-plist | 1 + 3 files changed, 6 insertions(+), 5 deletions(-)