On Tue, Dec 21, 2021 at 05:32:16PM +0100, Lucas Nussbaum wrote: > Source: debian-faq > Version: 10.1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. <snip>
> > This is METAFONT, Version 2.71828182 (TeX Live 2022/dev/Debian) (preloaded > > base=mf) > > > > kpathsea: Running mktexmf nullfont > > > > ! I can't find file `nullfont'. > > <*> ...four; mag:=1; ; nonstopmode; input nullfont > > > > Please type another input file name > > ! Emergency stop. > > <*> ...four; mag:=1; ; nonstopmode; input nullfont > > > > Transcript written on mfput.log. > > grep: nullfont.log: No such file or directory > > mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; ; nonstopmode; > > input nullfont' failed to make nullfont.tfm. > > kpathsea: Appending font creation commands to missfont.log. > > xelatex failed > > stdin.tex:24: Package fontspec Error: The font "CharisSIL-R" cannot be > > found. <snip> > > stdin.tex:538: Font TU/CharisSIL-R.ttf(0)/b/n/12=[CharisSIL-B.ttf]/OT at > > 12.0pt not loadable: Metric (TFM) file or installed font not found. > > stdin.tex:538: leading text: T > > .:1787: Font TU/CharisSIL-R.ttf(0)/b/n/8=[CharisSIL-B.ttf]/OT at 8.0pt not > > loadable: Metric (TFM) file or installed font not found. > > .:1787: leading text: } > > Unexpected error occured > > Error: list index out of range > > make[2]: *** [Makefile:169: en/debian-faq.en.pdf] Error 1 > > > The full build log is available from: > http://qa-logs.debian.net/2021/12/20/debian-faq_10.1_unstable.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > If you reassign this bug to another package, please marking it as > 'affects'-ing > this package. See https://www.debian.org/Bugs/server-control#affects > > If you fail to reproduce this, please provide a build log and diff it with > mine > so that we can identify if something relevant changed in the meantime. Thank you for reporting this, and thank you for your massive rebuild efforts: much appreciated. I'll look into this issue soonishlish. Bye, Joost
