From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: texlive2019-bin: use historic texlive repository
Date: Mon, 11 May 2020 22:16:14 +0200 [thread overview]
Message-ID: <20200511201614.nSEIkxqhEUlhkI09t1XExFri-bwJMcGmG065HPBz1K4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20913@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
There's a merged pull request on the void-packages repository
texlive2019-bin: use historic texlive repository
https://github.com/void-linux/void-packages/pull/20913
Description:
Currently a fresh texlive installation fails.
As texlive2020 has been released the default repository no longer
contains the 2019 version. Make the installer use the frozen
historic one.
Also the signing key seems to be expired so the installer fails. A workaround
is disabling the verification. However, not sure if this is a good idea, but I couldn’t
make it work otherwise.
This is likely a problem for the other historic texlive versions in Void’s repository, too, I didn’t test, however.
@leahneukirchen
prev parent reply other threads:[~2020-05-11 20:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 13:23 [PR PATCH] " newbluemoon
2020-04-12 13:37 ` leahneukirchen
2020-04-12 13:38 ` leahneukirchen
2020-04-12 13:39 ` leahneukirchen
2020-04-12 14:04 ` leahneukirchen
2020-04-12 14:06 ` leahneukirchen
2020-04-12 14:26 ` leahneukirchen
2020-04-12 18:04 ` newbluemoon
2020-04-21 20:42 ` ericonr
2020-04-21 20:57 ` leahneukirchen
2020-04-23 8:10 ` leahneukirchen
2020-04-23 11:14 ` newbluemoon
2020-04-23 17:27 ` [PR PATCH] [Updated] " newbluemoon
2020-04-23 17:28 ` newbluemoon
2020-04-26 6:25 ` [PR PATCH] [Updated] " newbluemoon
2020-05-10 17:34 ` newbluemoon
2020-05-11 20:10 ` newbluemoon
2020-05-11 20:16 ` leahneukirchen [this message]
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=20200511201614.nSEIkxqhEUlhkI09t1XExFri-bwJMcGmG065HPBz1K4@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).