From: elaexuotee--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 40558@debbugs.gnu.org
Subject: bug#40558: Modular TexLive "Insufficient extension fonts" and duplicate fonts
Date: Sun, 23 Jan 2022 11:53:25 +0900 [thread overview]
Message-ID: <2JED6QHA0S33Q.3I79W95FRDN8Q@wilsonb.com> (raw)
In-Reply-To: <87o844p5sj.fsf@elephly.net>
> At least the question “is texlive-amsfonts broken” is definitively
> answered. This was what this issue was about, no? I’d rather keep the
> other issue separate.
Well, it's still broken in the sense that we're not able to typeset with
eufm10, no? That said, I guess it could make sense to define this issue as
"tlpdb non-conformance problems" and close as fixed.
next prev parent reply other threads:[~2022-01-23 2:54 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
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 [this message]
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=2JED6QHA0S33Q.3I79W95FRDN8Q@wilsonb.com \
--to=bug-guix@gnu.org \
--cc=40558@debbugs.gnu.org \
--cc=elaexuotee@wilsonb.com \
--cc=rekado@elephly.net \
/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).