First off, this mistake is my fault. The TeXLive 2025 work was complete and I started importing it into rawhide, and it got built (partially) during the Fedora 44 mass rebuild. The good news: it will be ready before Fedora 44. The bad news: this change/feature was supposed to land in Fedora 45. Whoops.
We've got three options: 1. We change the feature target to Fedora 44. 2. We untag all the new texlive packages (including the updated texlive-base) and rebuild everything dependent that was rebuilt with the new texlive. 3. We untag all the new texlive packages and just let everything keep the docs it generated with the newer packages, even though they might not render the same on the next rebuild
I'm asking FESCo to approve Option #1. The work is done (well, very very close to done, only a handful of packages left to review/import/build) and it will make a lot of users happy.
As unfortunate as this is... At least it's pretty much done-ish? So +1 to land it for F44.
I'm also marking this for fast track as this is technically done and this is for reconciling things quickly.
Metadata Update from @ngompa: - Issue set to the milestone: Fedora Linux 44 - Issue tagged with: fast track
Yep, no need to wait if it's mostly done. (And TeXLive is a leaf package, so even if it's not quite done at this point, I don't think there's any problem with pushing it after beta.)
+1
+1 to finishing the work in F44.
And TeXLive is a leaf package
It's definitely not a leaf package.
+1 to moving to f44.
0 from me. I think options 1 and 3 are equally valid choices here.
Option 3 would be messy since it would require git reverts across the board to fix everything.
+1 from me
Whoops, I should have said for which option. +1 to moving to F44.
Let's discuss this during the meeting today (18:00 GMT in https://matrix.to/#/#meeting:fedoraproject.org).
Metadata Update from @zbyszek: - Issue tagged with: meeting
Is that really necessary? It's on track to just be accepted for F44 by tomorrow. Or, given that Freeze is today, if at least one more person votes +1, I can be convinced to switch my 0 to a +1 to get it done in time.
+1 for fast-tracking to F44 - hopefully in time? Sorry, still catching up after conference + vacation travels
It's all landed in F44 now, so thanks folks.
This was discussed during the meeting today: APPROVED (+7, 1, 0)
Metadata Update from @zbyszek: - Issue untagged with: meeting - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)