From: "Ludovic Courtès" <ludo@gnu.org>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>
Cc: 48064@debbugs.gnu.org
Subject: bug#48064: texlive-* packages fail to build non-deterministically
Date: Mon, 05 Jul 2021 10:42:55 +0200 [thread overview]
Message-ID: <87k0m5w3qo.fsf@gnu.org> (raw)
In-Reply-To: <3617506.ZDHn73UUgp@popigai> (Thiago Jung Bauermann's message of "Tue, 29 Jun 2021 16:59:48 -0300")
Hello!
Thiago Jung Bauermann <bauermann@kolabnow.com> skribis:
> I have bad news and good news. :-)
>
> Unfortunately, TeX Live 2021 still has this bug. I tested version 20210325
> (which is the latest on the historic TeX Live FTP site), with subversion
> tag texlive-2021.3 (which is the latest tag in the TeX Live repo).
Bah. Still, if you have the whole texlive upgrade, we should apply it!
> The good news is that I found a simple workaround: use pdftex instead of
> luatex to build the affected packages. I am currently building all packages
> matching ‘^texlive’ a few times to find the ones needing this workaround.
> So far, I found these:
>
> • texlive-amsfonts
> • texlive-amscls
> • texlive-babel
> • texlive-babel-swedish
> • texlive-latex-amsmath
> • texlive-generic-babel-english
> • texlive-latex-cyrillic
> • texlive-latex-graphics
> • texlive-latex-tools
We haven’t heard from dev-luatex yet. I think we should go with this
workaround for now (those build failures are frequently preventing
evaluations at <https://ci.guix.gnu.org/jobset/core-updates> from
completing, which is a real bummer). Does using ‘pdftex’ rather than
‘luatex’ have an impact on the output of these packages?
Thanks!
Ludo’.
next prev parent reply other threads:[~2021-07-05 8:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 15:39 bug#48064: texlive-* packages fail to build non-deterministically Ludovic Courtès
2021-06-06 1:36 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2021-06-29 14:02 ` Ludovic Courtès
2021-06-29 15:10 ` Ludovic Courtès
2021-06-30 11:53 ` bug#48064: [Dev-luatex] " luigi scarso
2021-07-02 15:11 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2021-12-31 17:40 ` luigi scarso
2021-06-09 0:28 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2021-06-30 10:05 ` Ludovic Courtès
2021-06-30 12:46 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2021-06-30 14:54 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2021-07-01 13:07 ` Ludovic Courtès
2021-07-02 15:17 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2021-06-29 19:59 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2021-07-05 8:42 ` Ludovic Courtès [this message]
2021-07-02 16:00 ` bug#48064: [PATCH core-updates] build-system/texlive: Change default format to pdftex Thiago Jung Bauermann via Bug reports for GNU Guix
2021-07-05 9:20 ` bug#48064: texlive-* packages fail to build non-deterministically Ludovic Courtès
2021-07-05 17:27 ` Thiago Jung Bauermann 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=87k0m5w3qo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=48064@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
/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).