sys-apps/uutils-coreutils-bin
GNU coreutils rewritten in Rust (prebuilt upstream binaries)
ChangeLog
commit cc5bb86636f61f6b58a0b053e599e5f7c6793cbb
Author: lucascouts <lucascs@protonmail.com>
Date: Thu Sep 17 22:25:23 2026 -0300
bump 24 packages; fix the tlottie/telegram-desktop static-link pin
Batch autoupdate sweep, plus three things the applier could not have done
on its own.
tlottie/telegram-desktop -- the proposed bump was wrong.
The autoupdate offered tlottie 0.1.0_pre20260908. Telegram v7.2.9's
prepare.py pins commit 31f1b542f8, dated 2026-09-11, and v7.2.9 newly
applies tlottie.patch from desktop-app/patches (pinned there at
519aaa0846). tlottie is linked STATICALLY into the Telegram binary, so a
wrong pin is an ABI mismatch with no soname to catch it. Bumped to
0.1.0_pre20260911 with files/tlottie-tdesktop-compat.patch (six hunks over
three files; verified with both `git apply --check` and eapply's own flag
set against a real checkout of the pinned commit), and revbumped
telegram-desktop to 7.2.9-r1 with the matching floor.
check-tlottie-pin.sh had a false negative.
Its detector anchored the category right after leading whitespace, so any
version-range prefix made the atom invisible and it reported "declares no
dependency on media-libs/tlottie". Widened the detector rather than
dropping the floor: the floor is the only thing that forces a rebuild on
someone who already has the old archive installed, precisely because the
linkage is static. Self-test grew 17 -> 23 assertions covering bare,
floored and slotted atoms as matches, and comment, blocker and
prefix-lookalike as non-matches.
uutils-coreutils-bin 0.12.0 changed its documentation source.
Upstream dropped the architecture-independent docs.tar.zst and now ships a
`uudoc` binary beside the payload. The ebuild derives the applet list from
`coreutils --list` and renders man pages and completions through uudoc,
which means the build host must be able to execute the target binary --
src_install dies with an explicit message when it cannot. Verified by
running the payload: all 106 applets render a man page and bash, zsh and
fish completions with no failure, and the completion sed anchors still
match.
dev-db/redis returns as an ahead-of-::gentoo mirror.
It was removed on 2026-09-07 because the ::gentoo ebuild had gained a zstd
USE flag this copy lacked. That is no longer true: the ebuild here is
byte-identical to ::gentoo's 8.10.1, zstd included, one release ahead at
8.10.2. The record carries the condition that closes it again -- drop it
once ::gentoo ships >=8.10.2.
Carried forward deliberately, not re-derived from a stale base:
mt7927-dkms -r1 (MT6639 BT firmware ungated from USE=btmtk, needed because
the kernel's own btmtk wants it) and nvidia-cuda-toolkit -r1 (GCC_MAX 15
-> 16, CLANG_MAX 21 -> 22, two targets/ globs fixed to ${narch} for
arm64/sbsa).
Verification, all local:
- pkgcheck on the 20 touched packages: no finding that is not also present
on the previous version.
- check-tlottie-pin.sh exits 0 (was 1); check-slot-naming-contract.sh and
check-autoupdate-damage.sh exit 0.
- gentoo-parity.sh: 0 ALIGN, 0 packages behind ::gentoo, [missing] 0,
[digest] 0, [orphans] 4 (the documented floor), and [cache] back from 14
to 0 -- the stale entries were the killed applier's leftovers.
- md5-cache _md5_ matches the ebuild md5sum for all 25 new ebuilds.
Nothing was merged or compiled: this host has no sudo and Portage reads
/var/db/repos/bentoo, not the checkout. The evidence above is fetch-and-
hash, static analysis and running the uutils payload -- not a build.
Pre-existing and left alone, outside this batch's scope:
sys-power/upower-1.91.4 installs a systemd unit with no OpenRC counterpart
(check-openrc-coverage.sh FAIL, from commit 43e3f0617), and
mail-client/thunderbird{,-l10n}-156.0 account for the sweep's remaining
2 UNDOCUMENTED and 1 REDUNDANT rows.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
commit a628ffe08db2ab07e73746f83b77900c8b87a705
Author: lucascouts <lucascs@protonmail.com>
Date: Mon Aug 31 22:57:38 2026 -0300
add(metadata/{md5-cache/app-admin/awscli2-2.36.36, md5-cache/app-editors/kiro-1.0.411, md5-cache/dev-python/uv-bin-0.12.8, md5-cache/dev-util/claude-code-2.1.252, md5-cache/dev-util/mesa_clc-26.3.0_pre20260901, md5-cache/media-libs/mesa-26.3.0_pre20260901, md5-cache/media-libs/vulkan-layers-1.4.361_p20260901, md5-cache/media-libs/vulkan-loader-1.4.361_p20260831, md5-cache/sci-ml/ik_llama-cpp-0_pre20260831, md5-cache/sci-ml/llama-swap-252, md5-cache/sys-apps/pnpm-11.25.0, md5-cache/sys-apps/uutils-coreutils-bin-0.11.0}), mod(.autoupdate/packages.toml), up(app-admin/awscli2-2.36.34 -> 2.36.36, app-editors/kiro-1.0.395 -> 1.0.411, dev-python/uv-bin-0.12.7 -> 0.12.8, dev-util/{claude-code-2.1.251 -> 2.1.252, mesa_clc-26.3.0_pre20260831 -> 26.3.0_pre20260901}, media-libs/{mesa-26.3.0_pre20260831 -> 26.3.0_pre20260901, vulkan-layers-1.4.361_p20260831 -> 1.4.361_p20260901, vulkan-loader-1.4.361_p20260829 -> 1.4.361_p20260831}, sci-ml/{ik_llama-cpp-0_pre20260828 -> 0_pre20260831, llama-swap-251 -> 252}, sys-apps/{pnpm-11.24.0 -> 11.25.0, uutils-coreutils-bin-0.10.0 -> 0.11.0})
commit 05b58fec548990c07507257a21abb82703ccb8ff
Author: lucascouts <lucascs@protonmail.com>
Date: Thu Aug 6 12:15:50 2026 -0300
add(sys-apps/{fakeroot-2.1.4,uutils-coreutils-0.10.0,uutils-coreutils-bin-0.10.0}), mod(.autoupdate/packages.toml)
fakeroot 2.1.4: ::gentoo is on 1.33 (2025) while Debian, where fakeroot is
developed, moved to the 2.x series in July 2026. The tarball is .orig.tar.xz
now; the configure-id_t patch is upstream since 1.35.1 and the musl patch was
rebased down to its faked.c half (the libfakeroot.c half is upstream too).
Autotools is kept over the new meson build because that is where the po4a man
page translations are wired. t.xattr2 is skipped exactly as Debian skips it.
Tests: 16 pass, 1 skip, 0 fail.
uutils-coreutils 0.10.0: temporary mirror. ::gentoo builds it from a
consolidated crate tarball that github.com/gentoo-crate-dist had not published
for this release, so the ~400 crates are listed inline and fetched from
crates.io instead; nothing is self-hosted. cargo.eclass only computes
CARGO_CRATE_URIS, so SRC_URI has to consume it -- the ::gentoo ebuild never
does because its CRATES is empty. Verified by compiling with network-sandbox
on, which proves the block is complete.
uutils-coreutils-bin 0.10.0: not a mirror -- ::gentoo ships no binary variant.
Installs upstream's prebuilt multicall binary with the same uu- prefixed layout
as the from-source package, so the two block each other. glibc builds on
amd64/x86, static musl on arm64/riscv (upstream publishes no glibc tarball for
those). PMS does not know the .tar.zst suffix even in EAPI 8, so unpacker.eclass
handles the docs archive that carries the man pages and completions.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: lucascouts <lucascs@protonmail.com>
Date: Thu Sep 17 22:25:23 2026 -0300
bump 24 packages; fix the tlottie/telegram-desktop static-link pin
Batch autoupdate sweep, plus three things the applier could not have done
on its own.
tlottie/telegram-desktop -- the proposed bump was wrong.
The autoupdate offered tlottie 0.1.0_pre20260908. Telegram v7.2.9's
prepare.py pins commit 31f1b542f8, dated 2026-09-11, and v7.2.9 newly
applies tlottie.patch from desktop-app/patches (pinned there at
519aaa0846). tlottie is linked STATICALLY into the Telegram binary, so a
wrong pin is an ABI mismatch with no soname to catch it. Bumped to
0.1.0_pre20260911 with files/tlottie-tdesktop-compat.patch (six hunks over
three files; verified with both `git apply --check` and eapply's own flag
set against a real checkout of the pinned commit), and revbumped
telegram-desktop to 7.2.9-r1 with the matching floor.
check-tlottie-pin.sh had a false negative.
Its detector anchored the category right after leading whitespace, so any
version-range prefix made the atom invisible and it reported "declares no
dependency on media-libs/tlottie". Widened the detector rather than
dropping the floor: the floor is the only thing that forces a rebuild on
someone who already has the old archive installed, precisely because the
linkage is static. Self-test grew 17 -> 23 assertions covering bare,
floored and slotted atoms as matches, and comment, blocker and
prefix-lookalike as non-matches.
uutils-coreutils-bin 0.12.0 changed its documentation source.
Upstream dropped the architecture-independent docs.tar.zst and now ships a
`uudoc` binary beside the payload. The ebuild derives the applet list from
`coreutils --list` and renders man pages and completions through uudoc,
which means the build host must be able to execute the target binary --
src_install dies with an explicit message when it cannot. Verified by
running the payload: all 106 applets render a man page and bash, zsh and
fish completions with no failure, and the completion sed anchors still
match.
dev-db/redis returns as an ahead-of-::gentoo mirror.
It was removed on 2026-09-07 because the ::gentoo ebuild had gained a zstd
USE flag this copy lacked. That is no longer true: the ebuild here is
byte-identical to ::gentoo's 8.10.1, zstd included, one release ahead at
8.10.2. The record carries the condition that closes it again -- drop it
once ::gentoo ships >=8.10.2.
Carried forward deliberately, not re-derived from a stale base:
mt7927-dkms -r1 (MT6639 BT firmware ungated from USE=btmtk, needed because
the kernel's own btmtk wants it) and nvidia-cuda-toolkit -r1 (GCC_MAX 15
-> 16, CLANG_MAX 21 -> 22, two targets/ globs fixed to ${narch} for
arm64/sbsa).
Verification, all local:
- pkgcheck on the 20 touched packages: no finding that is not also present
on the previous version.
- check-tlottie-pin.sh exits 0 (was 1); check-slot-naming-contract.sh and
check-autoupdate-damage.sh exit 0.
- gentoo-parity.sh: 0 ALIGN, 0 packages behind ::gentoo, [missing] 0,
[digest] 0, [orphans] 4 (the documented floor), and [cache] back from 14
to 0 -- the stale entries were the killed applier's leftovers.
- md5-cache _md5_ matches the ebuild md5sum for all 25 new ebuilds.
Nothing was merged or compiled: this host has no sudo and Portage reads
/var/db/repos/bentoo, not the checkout. The evidence above is fetch-and-
hash, static analysis and running the uutils payload -- not a build.
Pre-existing and left alone, outside this batch's scope:
sys-power/upower-1.91.4 installs a systemd unit with no OpenRC counterpart
(check-openrc-coverage.sh FAIL, from commit 43e3f0617), and
mail-client/thunderbird{,-l10n}-156.0 account for the sweep's remaining
2 UNDOCUMENTED and 1 REDUNDANT rows.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
commit a628ffe08db2ab07e73746f83b77900c8b87a705
Author: lucascouts <lucascs@protonmail.com>
Date: Mon Aug 31 22:57:38 2026 -0300
add(metadata/{md5-cache/app-admin/awscli2-2.36.36, md5-cache/app-editors/kiro-1.0.411, md5-cache/dev-python/uv-bin-0.12.8, md5-cache/dev-util/claude-code-2.1.252, md5-cache/dev-util/mesa_clc-26.3.0_pre20260901, md5-cache/media-libs/mesa-26.3.0_pre20260901, md5-cache/media-libs/vulkan-layers-1.4.361_p20260901, md5-cache/media-libs/vulkan-loader-1.4.361_p20260831, md5-cache/sci-ml/ik_llama-cpp-0_pre20260831, md5-cache/sci-ml/llama-swap-252, md5-cache/sys-apps/pnpm-11.25.0, md5-cache/sys-apps/uutils-coreutils-bin-0.11.0}), mod(.autoupdate/packages.toml), up(app-admin/awscli2-2.36.34 -> 2.36.36, app-editors/kiro-1.0.395 -> 1.0.411, dev-python/uv-bin-0.12.7 -> 0.12.8, dev-util/{claude-code-2.1.251 -> 2.1.252, mesa_clc-26.3.0_pre20260831 -> 26.3.0_pre20260901}, media-libs/{mesa-26.3.0_pre20260831 -> 26.3.0_pre20260901, vulkan-layers-1.4.361_p20260831 -> 1.4.361_p20260901, vulkan-loader-1.4.361_p20260829 -> 1.4.361_p20260831}, sci-ml/{ik_llama-cpp-0_pre20260828 -> 0_pre20260831, llama-swap-251 -> 252}, sys-apps/{pnpm-11.24.0 -> 11.25.0, uutils-coreutils-bin-0.10.0 -> 0.11.0})
commit 05b58fec548990c07507257a21abb82703ccb8ff
Author: lucascouts <lucascs@protonmail.com>
Date: Thu Aug 6 12:15:50 2026 -0300
add(sys-apps/{fakeroot-2.1.4,uutils-coreutils-0.10.0,uutils-coreutils-bin-0.10.0}), mod(.autoupdate/packages.toml)
fakeroot 2.1.4: ::gentoo is on 1.33 (2025) while Debian, where fakeroot is
developed, moved to the 2.x series in July 2026. The tarball is .orig.tar.xz
now; the configure-id_t patch is upstream since 1.35.1 and the musl patch was
rebased down to its faked.c half (the libfakeroot.c half is upstream too).
Autotools is kept over the new meson build because that is where the po4a man
page translations are wired. t.xattr2 is skipped exactly as Debian skips it.
Tests: 16 pass, 1 skip, 0 fail.
uutils-coreutils 0.10.0: temporary mirror. ::gentoo builds it from a
consolidated crate tarball that github.com/gentoo-crate-dist had not published
for this release, so the ~400 crates are listed inline and fetched from
crates.io instead; nothing is self-hosted. cargo.eclass only computes
CARGO_CRATE_URIS, so SRC_URI has to consume it -- the ::gentoo ebuild never
does because its CRATES is empty. Verified by compiling with network-sandbox
on, which proves the block is complete.
uutils-coreutils-bin 0.10.0: not a mirror -- ::gentoo ships no binary variant.
Installs upstream's prebuilt multicall binary with the same uu- prefixed layout
as the from-source package, so the two block each other. glibc builds on
amd64/x86, static musl on arm64/riscv (upstream publishes no glibc tarball for
those). PMS does not know the .tar.zst suffix even in EAPI 8, so unpacker.eclass
handles the docs archive that carries the man pages and completions.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>


View
Download
Browse