From: Jochen Wiedmann <jochen.wiedmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: gsftopk: fatal: map file `psfonts.map' not found.
Date: Fri, 24 Jun 2022 13:10:00 -0700 (PDT) [thread overview]
Message-ID: <caf0db58-9600-44cf-9963-8401c1900fd3n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1954 bytes --]
Hi,
I am getting the errors below while running pandoc on AlmaLinux 8.
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600
ts1-lmr10
gsftopk: fatal: map file `psfonts.map' not found.
mktexpk: don't know how to create bitmap font for ts1-lmr10.
mktexpk: perhaps ts1-lmr10 is missing from the map file.
kpathsea: Appending font creation commands to missfont.log.
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600
ts1-lmr10
gsftopk: fatal: map file `psfonts.map' not found.
mktexpk: don't know how to create bitmap font for ts1-lmr10.
mktexpk: perhaps ts1-lmr10 is missing from the map file.
kpathsea: Appending font creation commands to missfont.log.
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600
ts1-lmr10
gsftopk: fatal: map file `psfonts.map' not found.
mktexpk: don't know how to create bitmap font for ts1-lmr10.
mktexpk: perhaps ts1-lmr10 is missing from the map file.
kpathsea: Appending font creation commands to missfont.log.
Error producing PDF.
!pdfTeX error: pdflatex (file ts1-lmr10): Font ts1-lmr10 at 600 not found
==> Fatal error occurred, no output PDF file produced!
I can reproduce the issue with the folloing Dockerfile:
FROM almalinux:8.6
RUN dnf -y install epel-release dnf-plugins-core
RUN dnf -y config-manager --set-enabled powertools
RUN dnf -y install pandoc texlive-latex
RUN dnf -y install texlive-metafont texlive-ec texlive-gsftopk
COPY docs.md /tmp/docs.md
RUN pandoc -s -o /tmp/docs.pdf /tmp/docs.md
Any ideas?
Thanks,
Jochen
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/caf0db58-9600-44cf-9963-8401c1900fd3n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2549 bytes --]
reply other threads:[~2022-06-24 20:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=caf0db58-9600-44cf-9963-8401c1900fd3n@googlegroups.com \
--to=jochen.wiedmann-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).