public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: matoro <matoro_mailinglist_gentoo-dev@matoro.tk>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>,
	arm@gentoo.org, hppa@gentoo.org, tex@gentoo.org
Subject: Re: [gentoo-dev] TeX Live 2023 stabilization imminent
Date: Mon, 10 Jun 2024 11:01:37 -0400	[thread overview]
Message-ID: <2c2a1435baf717ac520e2119eadf06c5@matoro.tk> (raw)
In-Reply-To: <dc7a2b12-3cc7-4181-8666-7fbd82ca9971@gentoo.org>

On 2024-06-09 13:00, Florian Schmaus wrote:
> After many months of work, the stabilization of TeX Live 2023 is imminent.
> 
> I would first like to thank everyone who contributed, reported bugs, and 
> helped to make this happen. Special thanks goes to negril for providing the 
> initial prototype ebuilds that helped to get this going.
> 
> TeX Live 2023 got a major overhaul and new tooling. User-facing highlights 
> include
> - all binlinks and binscripts are now properly installed and in PATH
> - all manpages are now installed (due to upstream's design, only if USE=doc)
> - tlmgr is now available (but forced into user mode, as done by other 
> distributions)
> - the tlpdb is dynamically created, texdoc works (if USE=doc)
> 
> While I do not have any reason to believe that there are remaining issues 
> lurking in TeX Live 2023, I would like to use this as opportunity to 
> encourage advanced users to switch to TeX Live 2023 right now. Please report 
> issues that come up.
> 
> The re-keywording of TeX Live 2023 is ongoing in
>                      https://bugs.gentoo.org/932752.
> Unfortunately two stable arches are lacking: arm and hppa. It would be great 
> If the respective arch teams could prioritize the keywording. Otherwise, the 
> arches may missing out on the upcoming stabilization request.
> 
> - Flow

Hi Flow, I went ahead and started reviewing this bug for the remaining 
arches.  However when I ran it, I discovered that tests do not seem to run on 
the 2023 version, where they were previously being run on the 2021 version.  
In particular, I was trying to identify if https://bugs.gentoo.org/802672 was 
still present or not.  Are there any extra steps needed in order to get tests 
to run on the 2023 version?  If this could be looked at I can definitely get 
the remaining arches keyworded.


  reply	other threads:[~2024-06-10 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 17:00 [gentoo-dev] TeX Live 2023 stabilization imminent Florian Schmaus
2024-06-10 15:01 ` matoro [this message]
2024-06-10 20:14   ` Florian Schmaus

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=2c2a1435baf717ac520e2119eadf06c5@matoro.tk \
    --to=matoro_mailinglist_gentoo-dev@matoro.tk \
    --cc=arm@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=hppa@gentoo.org \
    --cc=tex@gentoo.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