From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Peter Neidhardt <pe.neidhardt@googlemail.com>, 27217@debbugs.gnu.org
Subject: bug#27217: texlive is too big
Date: Thu, 10 Jan 2019 13:15:18 +0100 [thread overview]
Message-ID: <87h8egd7zd.fsf@gnu.org> (raw)
In-Reply-To: <87zhs84urk.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 10 Jan 2019 12:27:59 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hello!
>>
>> I was also looking at the remaining dependencies on ‘texlive’. For
>> ‘teximpatient’, it looks like we’d need
>> <https://ctan.org/pkg/mflogo-font> but:
[...]
>> Throw to key `srfi-34' with args `(#<condition &invoke-error [program: "svn" arguments: ("checkout" "--non-interactive" "--trust-server-cert" "-r" "44591" "svn://mwww.tug.org/texlive/tags/texlive-2017.1/Master/texmf-dist/source/latex/mflogo-font" "/tmp/guix-directory.lVf6gO") exit-status: 1 term-signal: #f stop-signal: #f] 2219000>)'.
>
> So it fetches the description from ctan.org just fine, but then cannot
> download the directory from the SVN repository.
>
> That’s because there is no such directory in the SVN repository; see:
>
> https://www.tug.org/svn/texlive/tags/texlive-2017.1/Master/texmf-dist/source/latex/
>
> There’s “mflogo”, but no “mflogo-font”.
“mflogo” appears to be a different thing though, it doesn’t contain the
font. I found the ‘logo’ font in ‘texlive-fonts-knuth-lib’ though!
Now I can’t find the ‘pplr’ font (actually Adobe’s Palatino).
Ludo’.
next prev parent reply other threads:[~2019-01-10 12:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 19:03 bug#27217: texlive is too big Ricardo Wurmus
2017-11-23 20:51 ` bug#27217: break up TeXlive for guix Matt Wette
2018-01-23 13:20 ` bug#27217: texlive is too big Mathieu Lirzin
2018-05-28 12:02 ` Ricardo Wurmus
2018-05-28 11:07 ` Peter Neidhardt
2018-05-28 11:58 ` Ricardo Wurmus
2018-05-28 12:53 ` Peter Neidhardt
2018-12-15 14:11 ` Pierre Neidhardt
2019-01-10 9:27 ` Ludovic Courtès
2019-01-10 9:49 ` Pierre Neidhardt
2019-01-10 12:30 ` Ricardo Wurmus
2019-01-10 12:51 ` Pierre Neidhardt
2019-01-10 15:34 ` Ricardo Wurmus
2019-01-10 16:01 ` Pierre Neidhardt
2019-01-10 16:11 ` Ricardo Wurmus
2019-01-10 17:47 ` Pierre Neidhardt
2019-01-10 18:50 ` Ricardo Wurmus
2019-01-10 18:56 ` Pierre Neidhardt
2019-01-10 19:01 ` Ricardo Wurmus
2019-01-10 11:27 ` Ricardo Wurmus
2019-01-10 12:15 ` Ludovic Courtès [this message]
2019-01-13 12:21 ` Ricardo Wurmus
2019-01-17 9:36 ` Ludovic Courtès
2019-01-17 9:41 ` Pierre Neidhardt
2019-01-17 10:39 ` Ricardo Wurmus
2019-01-17 10:43 ` Pierre Neidhardt
2019-01-17 11:01 ` Ricardo Wurmus
2019-03-02 14:13 ` Pierre Neidhardt
2019-03-03 14:32 ` Jelle Licht
2019-03-05 8:39 ` Pierre Neidhardt
2019-03-16 12:59 ` Pierre Neidhardt
2019-03-18 8:47 ` Ludovic Courtès
2019-03-19 21:36 ` Ricardo Wurmus
2019-03-20 7:47 ` Pierre Neidhardt
2019-03-22 21:01 ` Ludovic Courtès
2019-01-17 10:36 ` Ricardo Wurmus
2019-01-15 15:34 ` 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=87h8egd7zd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27217@debbugs.gnu.org \
--cc=pe.neidhardt@googlemail.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).