Created attachment 238864 [details] v1 (apply via "git am")
Created attachment 238881 [details] followup (uharfbuzz) Probably not strictly required as uharfbuzz 0.32 builds fine with harfbuzz 6.0.0.
Triage: * reporter is a committer, assign accordingly (thanks) * the patch keywork is deprecated.
(In reply to Graham Perrin from comment #2) Graham, exp-runs are portmgr@s duty. So as the flag exp-run=? the pr belongs to portmgr@. Once the exp-run succeeds, portmgr@ will assign it back to the submitter. mfg Tobias
Exp-run looks fine
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=ed434537ea390a343d5a6644eb67c45c4b5a6e97 commit ed434537ea390a343d5a6644eb67c45c4b5a6e97 Author: Jan Beich <jbeich@FreeBSD.org> AuthorDate: 2022-12-16 21:36:15 +0000 Commit: Jan Beich <jbeich@FreeBSD.org> CommitDate: 2022-12-27 08:35:20 +0000 print/harfbuzz: update to 6.0.0 Changes: https://github.com/harfbuzz/harfbuzz/releases/tag/6.0.0 Reported by: GitHub (watch releases) PR: 268424 Exp-run by: antoine print/harfbuzz-hb-view/pkg-plist | 1 + print/harfbuzz-icu/pkg-plist | 1 + print/harfbuzz/Makefile | 4 ++-- print/harfbuzz/distinfo | 6 +++--- print/harfbuzz/pkg-plist | 2 ++ 5 files changed, 9 insertions(+), 5 deletions(-)
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=4c59b39a147e724939a7108c27824f0b2484e59a commit 4c59b39a147e724939a7108c27824f0b2484e59a Author: Jan Beich <jbeich@FreeBSD.org> AuthorDate: 2022-12-17 19:21:48 +0000 Commit: Jan Beich <jbeich@FreeBSD.org> CommitDate: 2022-12-27 08:37:53 +0000 print/py-uharfbuzz: update to 0.33.0 Changes: https://github.com/harfbuzz/uharfbuzz/releases/tag/v0.33.0 Reported by: GitHub (watch releases) PR: 268424 Exp-run by: antoine print/py-uharfbuzz/Makefile | 4 ++-- print/py-uharfbuzz/distinfo | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-)