From: Ricardo Wurmus <rekado@elephly.net>
To: Mikhail Kryshen <mikhail@kryshen.net>
Cc: guix-devel@gnu.org, bug-guix@gnu.org
Subject: Re: TeX Live 2019 wanted
Date: Fri, 17 Jan 2020 09:53:00 +0100 [thread overview]
Message-ID: <87d0bixy4z.fsf@elephly.net> (raw)
In-Reply-To: <87blr3f4v0.fsf@kryshen.net>
Mikhail Kryshen <mikhail@kryshen.net> writes:
> - font files are missing from texlive-latex-lh (shouldn't it be called
> texlive-lh?).
Thank you, that’s a good one. Generally, the texlive-latex-* packages
are of the old type that may very well be incomplete. I’ll replace this
one with texlive-lh which will include all the source files as it
should.
Thanks for the report!
--
Ricardo
next parent reply other threads:[~2020-01-17 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878smdyn36.fsf@elephly.net>
[not found] ` <87blr3f4v0.fsf@kryshen.net>
2020-01-17 8:53 ` Ricardo Wurmus [this message]
2021-02-02 14:25 ` bug#39160: TeX Live 2019 wanted Maxim Cournoyer
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=87d0bixy4z.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=bug-guix@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mikhail@kryshen.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).