commit 9196804040640bd18790ea57abc554719cc5537b
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Oct 7 09:29:32 2026 +0200

sci-ml/hf_xet: add 1.7.0

Upstream's lockfile now carries the rustls 0.23.45 and aws-lc-rs moves
that the 1.6.0 lockfile patch added, so no patch is needed; CRATES are
regenerated and the crate license set is unchanged. quick-xml 0.26.0
still has advisories but is not compiled for either keyworded target.

sysinfo 0.39.6 declares rust-version 1.95, so RUST_MIN_VER moves from
1.89.0 to 1.95.0. pyproject.toml is unchanged.

commit d210113c6772e45725cf449c83b1a742c3d6a1d0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Oct 4 15:24:57 2026 +0200

sci-ml/hf_xet: update vendored crates for RustSec, revbump

Upstream's 1.6.0 lockfile pins crates with RustSec advisories that have
semver-compatible fixes. Carry the lockfile change as a patch and list
the newer crates:

rustls 0.23.37 -> 0.23.45 (RUSTSEC-2026-0285)

The patch header also lists 3 crates that move with these to satisfy the
newer requirements.

Upstream's lockfile already pins konst 0.4.3 and redb 3.1.1, which
declare rust-version 1.89, so the cargo eclass QA notice asks for a
higher floor than the 1.88 the ebuild carried; RUST_MIN_VER moves to
1.89.0 with this revbump.

h2 and quick-xml also have advisories but stay as upstream pinned them,
since the shipped build does not compile them.

cargo-audit reports nothing else for the patched lockfile.

commit bd230fc13186146df04c83867a80bde7923a417b
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Oct 3 18:18:34 2026 +0200

sci-ml/hf_xet: drop 1.5.2

::gentoo ships it with the same keywords, plus the test suite,
python3_15 and Rust 1.89 as minimum; ours only hid it. 1.6.0 stays.

commit b562a8ad6e2e6e9edbbc56c763affc3c6b612ba1
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Oct 2 20:55:55 2026 +0200

sci-ml/hf_xet: restore crate license marker, add ZLIB

pycargoebuild's in-place mode finds the crate LICENSE+= block by the
'# Dependent crate licenses' comment and refuses to run without it, so
the comment is functional, not decorative.

Both blocks lacked ZLIB, which one of the vendored crates carries.

commit a9f9eb0332561d2b9c09e36f0a1677533ac40719
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Sep 10 07:21:59 2026 +0200

sci-ml/hf_xet: trim 1.6.0 crate provenance

commit 91edaf3b1c2e1bd29f50d1c309032bb9fe342fc1
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Sep 10 07:21:59 2026 +0200

sci-ml/hf_xet: trim 1.5.2 crate provenance

commit 9fc8af64f03211be6b15bf5d55af6a9688d2d9ba
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Aug 14 09:41:53 2026 +0200

sci-ml/hf_xet: normalize copyright header

Use the overlay-wide required copyright range consistently across retained versions.

commit bb6819807d15cfd2af1c9cc7e4b4e1052e7711b3
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Aug 8 09:35:25 2026 +0200

sci-ml/hf_xet: drop 1.5.1

commit 7ff201e2b278a4d3670ce53f559dace4559e0cdc
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Aug 8 09:35:19 2026 +0200

sci-ml/hf_xet: add 1.6.0

commit d26e488d095396a8343a1053601f18f59982a8df
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:04:12 2026 +0200

*/*: drop dead Python targets from PYTHON_COMPAT

139 ebuilds across 65 packages still listed python3_10, python3_11 or
python3_13t. None of the three is a supported implementation any more:
gentoo's python-utils-r1 sets _PYTHON_ALL_IMPLS to python3_ plus
python3_t, and everything older falls into the branch commented
"implementations deprecated prior to EAPI 9 are fatal".

Inert today, which is why nothing caught it. Targets outside
_PYTHON_ALL_IMPLS are silently dropped rather than rejected, so they
never became USE flags and never produced a dependency atom -- an ebuild
declaring python3_ was only ever offering 12, 13 and 14.

Two reasons to clean them up anyway. The eclass branch they land in
dies for any EAPI other than 7 or 8, so all 139 are waiting to break on
the first EAPI 9 bump. And pkgcheck's OldPythonCompat is a git-scoped
check that only inspects ebuilds touched in a commit range, so it never
reports these on a full-tree scan and would instead fire on whichever
unrelated commit next touches one of them.

No revbump, because nothing observable changes. Verified on a sample
spanning every transformation shape that the python USE flags portage
offers are byte-identical before and after, and that a pkgcheck run
over all 65 packages returns a set-identical list of findings.

The eight python2_7 ebuilds are deliberately untouched: that target is
also absent from _PYTHON_ALL_IMPLS, but they reach it through the
_PYTHON_ALLOW_PY27 hatch in the overlay's forked python-utils-r1_py2.

commit a37a9c1dc972ec2b79846db36c1d2aaf6e78a129
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Jul 17 15:42:44 2026 +0200

sci-ml/hf_xet: add 1.5.2

commit d53f19c0a8325052a70a2f81bc7258481c89404d
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 30 14:25:45 2026 +0200

sci-ml/hf_xet: new package

Fork of ::gentoo's sci-ml/hf_xet bumped to 1.5.1 (::gentoo has 1.2.0).
First link of the chain to unblock vllm 0.24.0: huggingface_hub 1.21.0
requires hf-xet >=1.5.1, and transformers >=5.5.3 requires that hf_hub.

::gentoo's ebuild fetches a maintainer-generated crates tarball from
dev.gentoo.org; that doesn't exist for 1.5.1, so CRATES is inlined from
xet-core v1.5.1's hf_xet/Cargo.lock (429 crates) and SRC_URI uses
CARGO_CRATE_URIS instead. The 1.2.0 maturin patch is dropped: 1.5.1's
pyproject already removed the python-source line it targeted.