unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: 40558@debbugs.gnu.org
Subject: bug#40558: Modular TexLive "Insufficient extension fonts" and duplicate fonts
Date: Fri, 11 Feb 2022 20:39:05 +0100	[thread overview]
Message-ID: <87h795tcl1.fsf@elephly.net> (raw)
In-Reply-To: <87h7xenect.fsf@jlicht.xyz>

I can reproduce this with a simpler document:

--8<---------------cut here---------------start------------->8---
\documentclass{article}
\usepackage{amsfonts}
\begin{document}
\begin{equation}
    x
\end{equation}
\end{document}
--8<---------------cut here---------------end--------------->8---

and this manifest

--8<---------------cut here---------------start------------->8---
(specifications->manifest
 (list
  "texlive-base"
  "texlive-amsfonts-fixed"
;;  "texlive-latex-amsmath"
  ))
--8<---------------cut here---------------end--------------->8---


-- 
Ricardo




  reply	other threads:[~2022-02-11 19:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11 16:15 bug#40558: Modular TexLive "Insufficient extension fonts" and duplicate fonts Jelle Licht
2020-04-20 19:31 ` Jelle Licht
2022-02-11 19:39   ` Ricardo Wurmus [this message]
2020-05-09 10:47 ` bug#40558: (no subject) elaexuotee
2020-05-12 12:36   ` Jelle Licht
2020-10-26 22:10   ` Ricardo Wurmus
2021-02-03  9:57     ` elaexuotee--- via Bug reports for GNU Guix
2022-01-21 17:21       ` bug#40558: Modular TexLive "Insufficient extension fonts" and duplicate fonts Ricardo Wurmus
2022-01-21 23:42         ` elaexuotee--- via Bug reports for GNU Guix
2022-01-22  7:50           ` Ricardo Wurmus
2022-01-23  2:53             ` elaexuotee--- via Bug reports for GNU Guix
2022-01-23 10:55               ` Ricardo Wurmus
2022-02-11 14:58         ` zimoun
2022-02-15 16:34 ` Ricardo Wurmus

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=87h795tcl1.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=40558@debbugs.gnu.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.
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).