commit eada4f2dfda6dffdefb6af85ab85ade35c1704d2
Author: lucascouts <lucascs@protonmail.com>
Date: Mon Sep 7 11:12:25 2026 -0300

fix(dev-util/vulkan-tools, sys-apps/flatpak): two build/test breakages ::gentoo already patches, del(4 orphan patches), mod(8 ebuilds): tag the last PATCHES rows - ALIGN reaches zero

The last thirteen open findings: the eleven remaining PATCHES rows and the two
UNDOCUMENTED ones. With these the sweep reports 222 rows, ALL JUSTIFIED, and
exits 0 for the first time.

TWO REAL BREAKAGES.

dev-util/vulkan-tools is missing #include <ctime> in vulkaninfo.cpp and fails
to build against libc++ 23. The timing is the whole story and was measured
against the GitHub API, not guessed: EGIT_COMMIT here is 532e2c0e from
2026-09-04T02:24Z, and upstream's fix 462d9819 landed at 18:35Z the SAME DAY -
sixteen hours later. The snapshot missed it by one working day. The patch
carries a delete-me note naming the commit that obsoletes it, so eapply will
fail loudly at the next bump rather than rot silently.

sys-apps/flatpak, both ebuilds: tests/make-test-runtime.sh copies
/usr/lib/locale/C.* with no guard, so building the test runtime dies where that
glob matches nothing. ::gentoo adds "|| true"; checked both 1.18.2 and 1.19.0
tarballs and neither has it.

Both patches were renamed version-agnostic on the way in, which promptly created
three fresh UNDOCUMENTED rows - the comparator sees a different filename on each
side and cannot know the content matches. Tagged as such. Worth remembering:
copying a patch from ::gentoo does not close a PATCHES row, it changes what the
row says.

FOUR ORPHAN PATCHES DELETED, which is what the two UNDOCUMENTED rows were.
tdesktop-6.9.3-{no-dispatch,qt6-no-wayland,use-pkgconfig-for-cmark-gfm}.patch
and nodejs-24.11.1-gcc15-ppc.patch: no ebuild references any of them, and the
versions they name are long gone (telegram-desktop is at 7.2.5, nodejs at 24.20
and 26.8). They are recoverable from git if that judgement was wrong.

EIGHT TAGS, each measured by reverse-applying ::gentoo's patch against the
tarball this overlay actually ships:

liborcus, gn, networkmanager-openvpn reverse-apply cleanly - upstream took
the change, ::gentoo's is a backport
bleachbit upstream went FURTHER: 6.0.3's locale
regex also accepts three-digit region
codes the Gentoo patch does not
imath the patch edits src/python/config/
ModuleDefine.cmake and Imath 3.2 has no
src/ at all
vim-core ::gentoo applies six Gentoo distro
patches pinned at VIM_PATCHES_VERSION
9.1.1432, four hundred patchlevels
behind the 9.2.1037 shipped here

TWO OF THE EIGHT LEAVE SOMETHING OPEN, and say so in the tag rather than
implying it is settled:

sentry-native ::gentoo's no-fuzz-test patch does NOT apply - hunk 2 fails
against 0.16.5. So sentry_fuzz_json is still built and
registered under USE=test here, and their reason for disabling
it stands. Rebasing the patch is the fix.
xdg-desktop-portal their sandbox-disable-failing-tests patch does not apply
either, both hunks failing against 1.22.1. test_dynamiclauncher
.py and test_location.py are still listed and still want
pipewire, network and /dev/fuse. Their optional-gstreamer patch
is a different matter and must stay absent - it invents a USE
flag upstream does not have.

Verified. pkgcheck against a worktree at 6abe6fb56 is identical on all twelve
packages touched. Tarballs came from DISTDIR where cached and from upstream
otherwise - gitlab.com, github.com, download.gnome.org, distfiles.obentoo.org.
--self-test 24/24, shellcheck -S warning clean.

A20 re-measured 224 -> 222 with a note on what changes now: until today a rising
ALIGN count was ordinary, and from here any ALIGN at all is a NEW divergence
that arrived after 2026-09-07. The sweep is finally usable as a gate.

Four md5-cache orphans went with the egencache run: vim-core-9.2.1036,
bleachbit-6.0.2 and flatpak-1.18.1, none with an ebuild since earlier bumps.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit 496137166b434e64accf1516386c029dda39ddfc
Author: lucascouts <lucascs@protonmail.com>
Date: Mon Sep 7 10:27:51 2026 -0300

mod(9 packages): tag the last SLOT and IUSE divergences, mod(scripts/gentoo-parity.sh): re-measure A14, A15 and A16

Ten rows across the SLOT and IUSE axes, and none is a lag. Both axes reach zero
ALIGN with this; only PATCHES and INHERIT are left.

THE FIVE SLOT ROWS ARE ALL THE SAME SHAPE: a subslot that IS the library ABI,
moving with a release this overlay ships ahead of ::gentoo. imath 3/30 against
3/29, nettle 0/9-7 against 0/8-6 (the libnettle and libhogweed sonames upstream
bumped for 4.0), libqmi 0/5.12 against 0/5.11. None can be aligned without
shipping ::gentoo's older version, and none SHOULD be suppressed - a real
subslot bump is exactly what consumers must rebuild for, which is why the SLOT
suppression rule deliberately spares them.

nodejs is the exception and the reason the axis exists. Its bare "24" and "26"
against ::gentoo's 0/26 is the multislot layout: this overlay slots nodejs by
major so several install side by side with app-eselect/eselect-nodejs choosing
between them. Aligning the string would collapse the layout the eselect module
depends on. Both ebuilds tagged, because the SLOT key is per ebuild.

THE FIVE IUSE ROWS are flags the overlay does not expose, each following from a
divergence already recorded elsewhere: calibre's dropped python3_12/13 (the 9
series needs 3.14), imagemagick's verify-sig (the eclass is not inherited),
opencv's quirc (OpenCV 5 dropped the bundled copy), xdg-desktop-portal's
gstreamer (that flag comes from ::gentoo's own optional-gstreamer patch, not
upstream).

net-dns/bind-tools is the one worth reading. Both sides are dummy ebuilds whose
only job is forwarding flags to net-dns/bind, and ::gentoo's 9.18.0-r1 forwards
[caps?] to a package that has no caps flag - checked across every bind in
::gentoo, 9.18.38 through 9.20.27, and not one declares it. So this is not the
overlay missing a flag; it is the overlay declining to copy a dead one.

A14, A15 and A16 re-measured, ALIGN -> JUSTIFIED on the rows this commit tagged.
Nothing about the SLOT stage moved: what those three assert is that the row
SURVIVES rather than being folded away as a version artifact, and "none" is
still the value that would mean it was. A16 already mixed the two verdicts,
which is the clearest evidence the distinction was never ALIGN-versus-JUSTIFIED.

Verified. Every md5-cache delta is _md5_ and eclass reordering only - no IUSE,
no SLOT, no dependency field moved, which is what comment-only edits must
produce. pkgcheck against a worktree at ba223c88c is identical on all nine
packages. The sweep holds at 225 rows with ALIGN 48 -> 38 and JUSTIFIED 175 ->
185. --self-test 24/24, shellcheck -S warning clean.

Two md5-cache orphans went with the egencache run, imath-3.2.2 and
bind-tools-9.20.26, neither with an ebuild since earlier bumps.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit 2f5cd4029135f84edfca51c709b76489d0697f61
Author: lucascouts <lucascs@protonmail.com>
Date: Thu Aug 20 19:42:10 2026 -0300

add(metadata/{md5-cache/app-admin/awscli2-2.36.28, md5-cache/app-editors/vim-9.2.0990, md5-cache/app-editors/vim-core-9.2.0990, md5-cache/app-portage/bentoolkit-0.25.0, md5-cache/dev-go/staticcheck-0.8.0, md5-cache/dev-libs/imath-3.2.3, md5-cache/dev-util/claude-code-2.1.238, md5-cache/dev-util/codex-0.149.0, md5-cache/dev-util/codex-bin-0.149.0, md5-cache/dev-util/mesa_clc-26.3.0_pre20260820, md5-cache/dev-util/vulkan-headers-1.4.360_p20260820, md5-cache/dev-util/vulkan-tools-1.4.360_p20260820, md5-cache/media-libs/mesa-26.3.0_pre20260820, md5-cache/media-libs/vulkan-layers-1.4.360_p20260820, md5-cache/media-libs/vulkan-loader-1.4.360_p20260820, md5-cache/net-libs/bun-bin-1.4.0, md5-cache/sci-ml/llama-cpp-0_pre10520, md5-cache/sci-ml/ollama-bin-0.32.15, md5-cache/sys-kernel/linux-firmware-20260820}), mod(.autoupdate/packages.toml), up(app-admin/awscli2-2.36.27 -> 2.36.28, app-editors/{vim, vim-core}-9.2.0984 -> 9.2.0990, app-portage/bentoolkit-0.24.0 -> 0.25.0, dev-go/staticcheck-0.7.0 -> 0.8.0, dev-libs/imath-3.2.2 -> 3.2.3, dev-util/codex{,-bin}-0.148.0 -> 0.149.0, media-libs/{mesa-26.3.0_pre20260819 -> 26.3.0_pre20260820, vulkan-layers-1.4.360_p20260819 -> 1.4.360_p20260820, vulkan-loader-1.4.360_p20260814 -> 1.4.360_p20260820}, net-libs/bun-bin-1.3.14 -> 1.4.0, sci-ml/{llama-cpp-0_pre10502 -> 0_pre10520, ollama-bin-0.32.14 -> 0.32.15}, sys-kernel/linux-firmware-20260818 -> 20260820)

commit b8390ab931bec93dd9690952b384e0ff41a8a26e
Author: lucascouts <lucascs@protonmail.com>
Date: Tue May 5 14:17:42 2026 -0300

add(dev-libs/imath-3.2.2)