Am 20.12.2022 um 04:08 teilte Danai SAE-HAN (韓達耐) mit:
Hi,
Sorry, I forgot all about this! I figured out it was a regression so in Unstable you need to go two versions back for Fontforge, which will ignore the warnings instead of halting the process. I'll be back home on 30 December. Meanwhile I'll send a message upstream.
With the latest upload of fontforge the issue is solved: #1015092 . We could simply close the bug or tighten the build dep. Hilmar -- sigfault
