From: Thiago Jung Bauermann <bauermann@kolabnow.com>
To: guix-devel@gnu.org
Subject: Re: [core-updates] texlive 2021 bootstrap problem
Date: Mon, 21 Jun 2021 21:43:19 -0300 [thread overview]
Message-ID: <20057949.yFzhkmNbUa@popigai> (raw)
In-Reply-To: <3693876.osayq9kAQP@popigai>
Hello,
Em terça-feira, 15 de junho de 2021, às 16:00:51 -03, Thiago Jung Bauermann
escreveu:
> Does anyone have an idea how to break this dependency loop? Do we need to
> have a package definition for a pre-2019-10 version of LaTeX just to
> build texlive-latex-l3kernel, and then use that as a dependency for the
> actual texlive-latex-base package?
I’m pursuing this option. I took the definition of texlive-latex-base from
the master branch (which doesn’t depend on LaTeX3) and added it to my
branch as texlive-latex-no-l3 (with a few minor changes to get it to build
with texlive 2021), and used it as a dependency to build texlive-latex-
l3kernel.
This worked! Now texlive-latex-l3kernel builds correctly, and the build of
texlive-latex-base is attempted (instead of just causing Guix to max out
its heap while trying to process a dependency loop, as it was doing
before). But the build fails when generating some latex formats – a problem
I’m still investigating.
But this is progress nevertheless. :-)
> If anyone wants to have a look at what I have so far, I pushed my patch
> to branch “bug-48064-texlive-2021” at https://gitlab.com/bauermann/guix
I just force-pushed this branch with my current version of the patches.
--
Thanks,
Thiago
next prev parent reply other threads:[~2021-06-22 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 19:00 [core-updates] texlive 2021 bootstrap problem Thiago Jung Bauermann
2021-06-22 0:43 ` Thiago Jung Bauermann [this message]
2021-06-24 18:26 ` Maxim Cournoyer
2021-06-24 20:53 ` Thiago Jung Bauermann
2021-06-25 3:34 ` Maxim Cournoyer
2021-06-25 5:00 ` Thiago Jung Bauermann
2021-06-29 20:43 ` Thiago Jung Bauermann
2021-06-30 16:21 ` Maxim Cournoyer
2021-07-05 0:24 ` Thiago Jung Bauermann
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=20057949.yFzhkmNbUa@popigai \
--to=bauermann@kolabnow.com \
--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).