all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: 40558-done@debbugs.gnu.org
Subject: bug#40558: Modular TexLive "Insufficient extension fonts" and duplicate fonts
Date: Tue, 15 Feb 2022 17:34:13 +0100	[thread overview]
Message-ID: <871r04ozns.fsf@elephly.net> (raw)
In-Reply-To: <874ktqxalv.fsf@jlicht.xyz>

This is now fixed with commit 64fcf9508af318cc2d71811815cfbe99063867b1.

The cause: we generated the tfm files from afm and pl files in a
misguided attempt to build as many things from “source” as possible.
Turns out that this results in bad tfm files.  These files mere meant to
be installed just as they are included in the upstream bundle.

That’s what we’re doing now.

-- 
Ricardo




      parent reply	other threads:[~2022-02-15 16:37 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
2022-01-23 10:55               ` Ricardo Wurmus
2022-02-11 14:58         ` zimoun
2022-02-15 16:34 ` Ricardo Wurmus [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871r04ozns.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=40558-done@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.