Bug#952481: texlive: mktexpk fails to create tcrm1000
Hi Holger,
On Mon, 24 Feb 2020, Holger Wansing wrote:
> http://qa-logs.debian.net/2020/02/22/installation-guide_20191229_unstable.log
What is there is
Writing build.out.el.amd64/html/index.html for book
Info: creating .pdf file...
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 tcrm1000
mkdir: cannot create directory ‘build.tmp.el.i386/dblatex/mt7684.tmp’: No such file or directory
kpathsea: Appending font creation commands to missfont.log.
which means that something in the build process is hosed .. either write
permissions or whatever, so this is strange.
Furthermore, by default these files are generated in /tmp, unless you
set TEMPDIR to something else, see /usr/share/texlive/texmf-dist/web2c/mktex.opt
if test -n "$TMPDIR"; then
TEMPDIR="${TMPDIR}/mt$$.tmp"
else
TEMPDIR="/tmp/mt$$.tmp"
fi
...
(umask 077 && mkdir "$TEMPDIR") || exit 1
So if $TMPDIR is not available, then there is something strange going
on.
Anyway, you **don't** want pk fonts (pixel fonts) in a PDF, so you
**should** depend on the
cm-super
fonts to get proper type1 fonts that are scalable (without pixelation).
My guess (wild guess) is the following:
- before tcrm fonts were not necessary because they were not used by the
LaTeX kernel, and thus no extra build process (mktex*) was called
- the new LaTeX kernel requires tc fonts (because textcomp is loaded)
- your package *always* had some setup that prevented creating of
directories or similar
- the recent changes made this obvious.
So as said, there are two things to be done:
- either make the directory writable, then the fonts will be generated
and included into the pdf properly
- depend on cm-super
or both.
Best
Norbert
--
PREINING Norbert https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Reply to: