From: Marius Bakke <mbakke@fastmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: TeX Live 2019 wanted
Date: Mon, 16 Dec 2019 23:41:57 +0100 [thread overview]
Message-ID: <87r213dhai.fsf@devup.no> (raw)
In-Reply-To: <87tv60c8fx.fsf@devup.no>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
Marius Bakke <mbakke@fastmail.com> writes:
> Andreas Enge <andreas@enge.fr> writes:
>
>> I gave it a try, dropped the patches, then the phase use-code-for-new-poppler
>> fails for texlive-bin; maybe these poppler phases can be dropped, but I am
>> not quite familiar with them.
>
> The 'use-code-for-new-poppler' phase needs to be rewritten along these
> lines (for both 2018 and 2019):
Errh, the patch only works if you already have Poppler 0.83.0. For the
current 'core-updates' branch, I believe you can use the same approach
but fetch poppler-0.76.0.cc instead (or take Arch's patch[0]).
[0] https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/texlive-bin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-12-16 22:42 UTC|newest]
Thread overview: 19+ 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 [this message]
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
2020-01-17 12:13 ` Ricardo Wurmus
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
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=87r213dhai.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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).