From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, 41211@debbugs.gnu.org
Subject: bug#41211: texlive-luatex-luaotfload fails to build
Date: Tue, 12 May 2020 23:15:22 +0200 [thread overview]
Message-ID: <87y2pwvor9.fsf@devup.no> (raw)
In-Reply-To: <87mu6d1b50.fsf@elephly.net>
merge 39755 41211
thanks
Thanks for the report. I tried updating texlive-lualatex-otfload a
while back, but gave up because the new versions needs "l3build" which I
have zero experience with. Any pointers for packaging and using l3build
appreciated.
For reference, as the original home page has been archived, here is the
updated repository with support for Tex Live 2019 and later:
https://github.com/latex3/luaotfload
next prev parent reply other threads:[~2020-05-12 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 14:27 bug#41211: texlive-luatex-luaotfload fails to build Ricardo Wurmus
2020-05-12 21:15 ` Marius Bakke [this message]
2023-10-21 15:21 ` 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
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=87y2pwvor9.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=41211@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 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).