commit 167aab613f29b6a832404f98695309972bb11edb
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jun 20 15:49:28 2026 +0200

dev-texlive/texlive-latex: Keyword 2025_p77034 for ~arm64

commit 2fca38218aff0b486dacf2c53bf483d3b59965a9
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jun 17 09:05:53 2026 +0200

dev-texlive/texlive-latex: Keyword 2026_p78733 for ~arm64

TeX Live LaTeX collection (texlive-module); architecture-independent (texmf + fmtutil-generated formats).

commit 33f29a09aeaedde8cc9ec11239ebb8d66f729381
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu May 28 21:43:54 2026 +0200

dev-texlive/texlive-latex: block pre-move collection versions

etoolbox (from latexrecommended) and lua-uni-algos (from luatex) relocated
into collection-latex in TL2025, and tagpdf (from latexextra) in TL2026.
Without a blocker an upgrade can merge the new texlive-latex, which now owns
those files, before the losing collection is upgraded to the version that
sheds them, aborting under FEATURES=protect-owned. Add soft !< blockers on
the pre-move collection versions, as ::gentoo does, so portage upgrades the
losing collection in the same transaction.

commit 6e8007a9dbd42c40b98b239fe8c96b1b1ed92f0b
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu May 28 13:55:46 2026 +0200

dev-texlive: sync collection membership to TL2025/2026 tlpdb

Phase F. Reconciled all collections' TEXLIVE_MODULE_
to the per-year tlpdb collection-depend lists via
reconcile-membership.py: +169 members for TL2025, +266 for
TL2026, and removed the handful that migrated out (lua-uni-algos
luatex->latex, etoolbox latexrecommended->latex, quantikz
mathscience->pictures, etc.).

Fixes two consequences of the revision-only regenerator: collections
that gained members upstream shipped incomplete (e.g. latex lacked
lua-uni-algos, which TL2025 expl3 needs for the lualatex format ->
"lua-uni-data not found"), and packages that moved collections
double-owned files, colliding on install against the TL2024 sibling
that still shipped them.

Membership now matches upstream; the collection self-entry and
luajittex OPTIONAL_ENGINE handling are preserved. Distfiles
re-manifested via the pinned RIT CTAN mirror.

commit 1a0c089b0e0dbb8aea6a173596d2993fd5443c4f
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu May 28 11:49:34 2026 +0200

dev-texlive/texlive-latex: add 2026_p78733

commit f294969cb9bbdbea01d6569d72aab9a16c564db5
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu May 28 00:36:31 2026 +0200

{app-text/texlive-core,dev-texlive/*}: drop TL2023-era NonexistentBlocker lines

Critical-review followup (#11). 5 ebuilds inherited '!<dev-texlive/X-2023'
blockers from ::tex-overlay's TL2023->TL2024 upgrade-ordering
enforcement. This overlay starts at TL2025; the 2023 atoms never
existed here, so pkgcheck flagged them as NonexistentBlocker
warnings on every scan. Strip the lines (and one orphan '# !<...
see https://bugs.gentoo.org/928307' comment).

Sweep targets:
app-text/texlive-core x4
dev-texlive/texlive-langcjk
dev-texlive/texlive-latex
dev-texlive/texlive-latexextra
dev-texlive/texlive-xetex

If a user upgrading from ::gentoo's TL2024 to ::stuff TL2025
hits a file collision, Portage will report it directly during merge;
the inherited blockers were paranoia about a transition we have no
relevance to.

commit b2d7fec7b9493dd30547a70f26ad2468690c6777
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed May 27 23:46:48 2026 +0200

dev-texlive: bump stale TL2024 dep references to TL2025 across all 39 collections

Critical-review followup to Phase D4. D4 dropped the TL_PV=2024
transitional pin so the eclass-derived '>=app-text/texlive-core-${PV
%%_*}' resolves to 2025, but the regenerator never substituted the
inline year references inherited verbatim from ::tex-overlay's TL2024
ebuilds:

>=app-text/texlive-core-2024[USE] -> -2025[USE] (6 ebuilds)
>=app-text/dvipsk-2024.03.11_p70015 -> -2025.03.08_p73850
>=dev-texlive/texlive-X-2024 -> -X-2025 (~15 ebuilds)

Functionally the overlay worked under the old form (>=2024 is
satisfied by 2025) but the bounds were misleading about our TL2025
lineage. Tightening to >=...-2025 makes the dep coherent. Users not
running ::stuff would never reach these ebuilds anyway: this
overlay's dev-texlive set IS the 2025 lineage.

pkgcheck after the sweep is unchanged: same 4 NonexistentBlocker
findings, no new issues introduced.

commit e1e97ca92f82a06f9f0a374fdd42a7f60086775b
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed May 27 23:30:37 2026 +0200

dev-texlive: drop transitional TL_PV=2024 pin across all 39 collections

texlive-module.eclass auto-derives RDEPEND=">=app-text/texlive-core-
$}", which for our 2025_pNNNNN PVs resolves to
">=app-text/texlive-core-2025". Phase B/C set TL_PV=2024 in each
ebuild to keep that dep solvable against ::gentoo's texlive-core-2024
while we had no TL2025 texlive-core. Phase D1 landed app-text/texlive
-core-2025, so the pin is no longer needed and is dropped uniformly
(plus its preceding rationale comment).

The per-package commit policy applies to per-package work; this is a
mechanical cross-cutting sweep with identical intent across all 39
collections, kept as one commit for review clarity. pkgcheck after
the sweep is unchanged: the same 4 NonexistentBlocker findings on
texlive-{latex,langcjk,xetex,latexextra} carried over from
::tex-overlay's TL2023-era ordering enforcement, no new issues.

commit 54b02973c3da9947ed1e01b2167b89c50c2b54f0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed May 27 17:04:06 2026 +0200

dev-texlive/texlive-latex: add 2025_p77034