From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: 65136@debbugs.gnu.org
Subject: bug#65136: mktexpk cannot create bitmap font for umvs
Date: Mon, 07 Aug 2023 23:10:21 +0200 [thread overview]
Message-ID: <874jlav9s2.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87tttak2w6.fsf@web.de> (Arne Babenhauserheide's message of "Mon, 07 Aug 2023 22:25:34 +0200")
Hello,
"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
> I restarted my system after a few weeks of uptime and now my LaTeX files
> no longer compile: I get the error
>
> kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+437/600 --dpi 1037 umvs
> mktexpk: don't know how to create bitmap font for umvs.
> mktexpk: perhaps umvs is missing from the map file.
>
> However it does work when I call
>
> guix shell texlive -- pdflatex -shell-escape file.tex
>
> My manifest contains as tex-relevant packages:
>
> "font-tex-gyre"
>
> "texinfo"
> "texlive"
> "texlive-ae"
> "texlive-amsfonts"
> "texlive-bin"
> "texlive-charter"
> "texlive-cm-super"
> "texlive-fontinst"
> "texlive-ec"
> "texlive-iwona"
> "texlive-latex-fonts"
> "texlive-rsfs"
> "texlive-inconsolata"
> "texlive-mdwtools"
> "texlive-ms"
> "texlive-polyglossia"
> "texlive-titlesec"
> "texlive-lh"
> "texlive-metafont"
> "texlive-mflogo"
> "texlive-mflogo-font"
> "texlive-palatino"
> "texlive-hyphen-complete"
> "texlive-times"
> "texlive-txfonts"
> "texlive-zapfding"
This setup is not correct, as you're mixing monolithic package
(`texlive') and an incomplete modular system (`texlive-*').
According to the manual, if you want to use modular TeX Live, you need
to provide at least a scheme or a collection, such as
`texlive-scheme-basic'. You should also remove `texlive'.
Does it work if you update your manifest?
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2023-08-07 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 20:25 bug#65136: mktexpk cannot create bitmap font for umvs Dr. Arne Babenhauserheide
2023-08-07 21:10 ` Nicolas Goaziou [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jlav9s2.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=65136@debbugs.gnu.org \
--cc=arne_bab@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).