From: Ricardo Wurmus <rekado@elephly.net>
To: Marius Bakke <mbakke@fastmail.com>, guix-devel@gnu.org
Subject: Re: TeX Live 2019 wanted
Date: Fri, 17 Jan 2020 13:13:46 +0100 [thread overview]
Message-ID: <871rryxoud.fsf@elephly.net> (raw)
In-Reply-To: <87tv51y4c8.fsf@devup.no>
Hey Marius,
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> I'll look into updating the remaining texlive packages shortly.
>
> Now this was some rocket science...
>
> The attached 9 patches updates everything (I think) to 2019.3.
This looks great!
It’s odd that they removed the few remaining scripts for generating
hyphenation patterns and replaced them with the output files, but it
sure simplifies some of these package definitions.
> The only regression I found from 'master' was that "discrover" fails to
> find math fonts during the build process.
Hmm, that’s a little worrying. I spent much more time than I think is
reasonable to work on The Font Problem in LaTeX. This really shouldn’t
break. I’m willing to investigate this, but it would be easier if we
had a branch for this upgrade and had ci.guix.gnu.org build it all.
I don’t want to build all these things on my laptop again.
--
Ricardo
next prev parent reply other threads:[~2020-01-17 12:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 19:06 TeX Live 2019 wanted Marius Bakke
2019-12-14 21:33 ` Pierre Neidhardt
2019-12-16 18:57 ` Andreas Enge
2019-12-16 19:49 ` Andreas Enge
2019-12-16 20:38 ` Marius Bakke
2019-12-16 22:20 ` Ricardo Wurmus
2019-12-16 22:41 ` Marius Bakke
2019-12-27 10:05 ` Andreas Enge
2020-01-09 22:10 ` Marius Bakke
2020-01-11 23:13 ` Marius Bakke
2020-01-12 10:13 ` Pierre Neidhardt
2020-01-12 10:40 ` Ricardo Wurmus
2020-01-12 13:19 ` Pierre Neidhardt
2020-01-12 14:49 ` Ricardo Wurmus
2020-01-12 15:00 ` Pierre Neidhardt
[not found] ` <87blr3f4v0.fsf@kryshen.net>
2020-01-17 8:53 ` Ricardo Wurmus
2020-01-21 10:25 ` Marco van Hulten
2021-02-02 14:25 ` bug#39160: " Maxim Cournoyer
2020-01-17 12:13 ` Ricardo Wurmus [this message]
2020-01-17 14:02 ` 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=871rryxoud.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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.