all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Texlive: Asymptote error: Math formula deleted: Insufficient symbol fonts.
Date: Thu, 21 Mar 2019 10:44:03 +0100	[thread overview]
Message-ID: <87sgvg36l8.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <877ect8bdr.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

Hi Ricardo,

Thanks for looking into this!

Before anything else, the issue is quite recent (max 4 weeks old) and it
used to work, so I'm wondering at this point if fontinst is not a red
herring.

Even then, we should also fix fontinst of course :)

Since we are on the verge of revamping our TeX packages, I'm stopping
the guessing game and I've looked at tlpdb.  So here is the deal:

2 packages:

- fontinst: depends on fontinst.ARCH, required only by
collection-fontutils. Contains some 100s files, most of which are
located in texmf-dist/tex/fontinst/.  Our texlive-tex-fontinst-base is
missing most of those.
  
- fontinst.ARCH: only contains bin/ARCH/fontinst.  Our texlive-bin has them.

So as far as I get it, our texlive-bin should be enough to generate a
full texlive-fontinst.  What do you think?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-03-21  9:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15  8:55 Texlive: Asymptote error: Math formula deleted: Insufficient symbol fonts Pierre Neidhardt
2019-03-16  9:51 ` Pierre Neidhardt
2019-03-20 21:35   ` Ricardo Wurmus
2019-03-20 21:49     ` Ricardo Wurmus
2019-03-21  9:44       ` Pierre Neidhardt [this message]
2019-03-21  9:53         ` Ricardo Wurmus
2019-03-21 10:17           ` Pierre Neidhardt

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=87sgvg36l8.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@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.