all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 36513@debbugs.gnu.org
Subject: [bug#36513] texlive-union: Build missing font maps.
Date: Mon, 15 Jul 2019 22:31:47 +0200	[thread overview]
Message-ID: <87muhfghu4.fsf@gnu.org> (raw)
In-Reply-To: <87d0ioschd.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 05 Jul 2019 17:54:54 +0200")

Hello,

Ricardo Wurmus <rekado@elephly.net> skribis:

>>From 11900d109a617d07e0085a25e747da76fcb12c2e Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Fri, 5 Jul 2019 17:48:45 +0200
> Subject: [PATCH] gnu: texlive-union: Build font maps.
>
> * gnu/packages/tex.scm (texlive-union)[arguments]: Execute updmap to generate
> missing font maps.
> [native-inputs]: Add coreutils, sed, and updmap.cfg.

I’m blissfully ignorant about TeX’s font maps, but I can say that this
fixes a warning about missing font maps that I had when using a
‘texlive-union’ as a package input.

Now, that probably leads to a big rebuild.  Can we estimate the number
of dependents?

Thank you!

Ludo’.

  reply	other threads:[~2019-07-15 20:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 15:54 [bug#36513] texlive-union: Build missing font maps Ricardo Wurmus
2019-07-15 20:31 ` Ludovic Courtès [this message]
2019-07-15 20:47   ` Ricardo Wurmus
2019-07-19 12:04     ` Ludovic Courtès
2019-07-22 19:28       ` Ricardo Wurmus
2019-07-22 20:19         ` Pierre Neidhardt
2019-07-22 21:27           ` Ricardo Wurmus
2019-09-04 13:37         ` Ludovic Courtès
2019-09-04 14:17           ` Ricardo Wurmus
2019-09-04 14:51             ` Pierre Neidhardt
2019-09-04 16:07               ` Ricardo Wurmus
2019-09-05  8:35             ` Ludovic Courtès
2020-10-17 10:07 ` bug#36513: " 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

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

  git send-email \
    --in-reply-to=87muhfghu4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36513@debbugs.gnu.org \
    --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 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.