From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 62493@debbugs.gnu.org
Subject: bug#62493: xelatex won't render fonts correctly without full texlive
Date: Wed, 29 Mar 2023 16:35:21 +0000 [thread overview]
Message-ID: <87cz4rh5xj.fsf@protonmail.com> (raw)
In-Reply-To: <87sfdnd11t.fsf@elephly.net>
"Ricardo Wurmus" <rekado@elephly.net> writes:
> John Kehayias <john.kehayias@protonmail.com> writes:
>
>> Exported revision 59745.
>> svn: E160013: File not found: revision 66702, path
>> '/tags/texlive-2021.3/Master/texmf-dist/tcode'
>> command "svn" "export" "--non-interactive" "--trust-server-cert"
>> "-r" "59745"
>> "svn://www.tug.org/texlive/tags/texlive-2021.3/Master/texmf-dist/tcode/"
>> "/tmp/guix-directory.XcAtR6/tcode/" failed with status 1
>
> The importer is naive and assumes that any file in tlpdb starts with
> “texmf-dist/”. For the xetex package there’s a file
> “tlpkg/tlpostcode/xetex.pl” and if you drop the same number of
> characters that you would for “texmf-dist/” you end up with
> “tcode/xetex.pl”.
>
> Oops!
Unfortunately that leaves me at a bit of a loss for making a
texlive-xetex package as I'm not understanding the whole texlive package
structure at first glance. I've tried something similar to other
packages I see but haven't gotten anywhere.
Any pointers or similar package to look at?
Thanks!
next prev parent reply other threads:[~2023-03-29 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 4:14 bug#62493: xelatex won't render fonts correctly without full texlive John Kehayias via Bug reports for GNU Guix
2023-03-28 10:12 ` Ricardo Wurmus
2023-03-28 11:51 ` Ricardo Wurmus
2023-03-29 15:21 ` John Kehayias via Bug reports for GNU Guix
2023-03-29 15:32 ` Ricardo Wurmus
2023-03-29 16:35 ` John Kehayias via Bug reports for GNU Guix [this message]
2023-03-29 20:18 ` Ricardo Wurmus
2023-03-29 19:35 ` John Kehayias via Bug reports for GNU Guix
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=87cz4rh5xj.fsf@protonmail.com \
--to=bug-guix@gnu.org \
--cc=62493@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--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).