Closed dkwo closed 3 years ago
@fosslinux @Chocimier
I get the following trying to output beamer slides from pandoc after the update:
pandoc --from markdown+task_lists -t beamer \
-V theme=metropolis \
-o slides.pdf slides.md
Error producing PDF.
! pdfTeX error (font expansion): auto expansion is only possible with scalable
fonts.
<argument> ...shipout:D \box_use:N \l_shipout_box
l.206 \end{frame}
This worked before the update with no changes.
I see the same issue as @dkwo when compiling well-formed LaTeX documents.
During the upgrade, the following error was printed for each texlive-*
package that was configured:
fmtutil [ERROR]: running `aleph -ini -jobname=lamed -progname=lamed *lambda.ini </dev/null' return status: 1
Downgrading texlive-core
to 2020.55416_2
(and the texlive-most
meta) instead prints
fmtutil [ERROR]: running `pdftex -ini -jobname=pdflatex-dev -progname=pdflatex-dev -translate-file=cp227.tcx *pdflatex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `xetex -ini -jobname=xelatex-dev -progname=xelatex-dev -etex xelatex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `luahbtex -ini -jobname=lualatex-dev -progname=lualatex-dev lualatex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `luatex -ini -jobname=dvilualatex-dev -progname=dvilualatex-dev dvilualatex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `pdftex -ini -jobname=latex-dev -progname=latex-dev -translate-file=cp227.tcx *latex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
but allows me to compile the aforementioned document again.
Wuh woh... I'll look into it.
This was an error with my testing setup that I overlooked. I will fix the error once gcc10 builds are over.
In the meantime, please run the following commands to fix it, fixed it for me in a clean Void install:
sed -i 's:`kpsewhich -var-value=TEXMFROOT`:"/usr/share/texmf-dist":' /usr/sbin/updmap
updmap-sys --syncwithtrees
updmap-sys
FWIW, the fix for this is to patch updmap in texlive and to add updmap
to the trigger... (hooray, even longer times for the trigger :|).
Sorry about that!
confirming that fixes it
Seems to work for me as well, but does not eliminate the fmtutil error that I noted earlier.
I have been unable to reproduce that fmtutil error. Can you please provide a list of all installed texlive-
packages and the output of aleph -ini -jobname=lamed -progname=lamed *lambda.ini </dev/null
.
I believe this error is harmless.
I doubt the aleph
error is related to this issue and I agree that it's harmless, but it is new with these texlive updates.
fmtutil-sys
run as in the XBPS trigger, but without --quiet
: fmtutil-sys.logaleph
run mentioend in fmtutil-sys
output: lamed.logIn the meantime, please run the following commands to fix it, fixed it for me in a clean Void install:
updmap-sys --syncwithtrees updmap-sys
Thanks, this solved the problem also on Haiku for me 👍
Since today's update, this fails for me
with