From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] texlive2019-bin: use historic texlive repository
Date: Sun, 26 Apr 2020 08:25:00 +0200 [thread overview]
Message-ID: <20200426062500.3-4NU9i3hiv9WeHVBmlrf88c-vapSCOBofffxXHrGYY@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: 885 bytes --]
There is an updated pull request by newbluemoon against master on the void-packages repository
https://github.com/newbluemoon/void-packages texlive2019-bin
https://github.com/void-linux/void-packages/pull/20913
texlive2019-bin: use historic texlive repository
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
A patch file from https://github.com/void-linux/void-packages/pull/20913.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-texlive2019-bin-20913.patch --]
[-- Type: text/x-diff, Size: 1734 bytes --]
From 44f293b4a4cb3f397d8704b8d4dc87f1902ee797 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Sun, 12 Apr 2020 15:02:31 +0200
Subject: [PATCH] texlive2019-bin: use historic texlive repository
As texlive2020 has been released the default repository no longer
contains the 2019 version. Make the installer use the frozen
historic one.
---
srcpkgs/texlive2019-bin/INSTALL | 4 ++--
srcpkgs/texlive2019-bin/template | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/texlive2019-bin/INSTALL b/srcpkgs/texlive2019-bin/INSTALL
index ea07e7ab407..c4fde28786b 100644
--- a/srcpkgs/texlive2019-bin/INSTALL
+++ b/srcpkgs/texlive2019-bin/INSTALL
@@ -5,10 +5,10 @@ post)
cd opt/texlive2019-installer
case "${ARCH}" in
x86_64-musl)
- ./install-tl -profile void.profile -force-platform x86_64-linuxmusl
+ ./install-tl -profile void.profile -repository https://ftp.tu-chemnitz.de/pub/tug/historic/systems/texlive/2019/tlnet-final/ -no-verify-downloads -force-platform x86_64-linuxmusl
;;
*)
- ./install-tl -profile void.profile
+ ./install-tl -profile void.profile -repository https://ftp.tu-chemnitz.de/pub/tug/historic/systems/texlive/2019/tlnet-final/ -no-verify-downloads
;;
esac
esac
diff --git a/srcpkgs/texlive2019-bin/template b/srcpkgs/texlive2019-bin/template
index 009d1d8d973..d7cd1c71664 100644
--- a/srcpkgs/texlive2019-bin/template
+++ b/srcpkgs/texlive2019-bin/template
@@ -1,7 +1,7 @@
-# Template file for 'texlive-bin'
+# Template file for 'texlive2019-bin'
pkgname=texlive2019-bin
version=2019
-revision=1
+revision=2
archs="x86_64* i686 aarch64 arm*"
maintainer="Leah Neukirchen <leah@vuxu.org>"
homepage="http://tug.org/texlive/"
next prev parent reply other threads:[~2020-04-26 6:25 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 ` newbluemoon [this message]
2020-05-10 17:34 ` [PR PATCH] [Updated] " newbluemoon
2020-05-11 20:10 ` newbluemoon
2020-05-11 20:16 ` [PR PATCH] [Merged]: " leahneukirchen
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=20200426062500.3-4NU9i3hiv9WeHVBmlrf88c-vapSCOBofffxXHrGYY@z \
--to=newbluemoon@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).