commit f459c6b406503af2fa3e4b30c3c51fca0b26dd13
Author: lucascouts <lucascs@protonmail.com>
Date: Tue Oct 13 13:34:13 2026 -0300

up(sys-kernel/gentoo-kernel-7.3_rc6 -> 7.3_rc7, virtual/dist-kernel-7.3_rc6 -> 7.3_rc7), mod(metadata/md5-cache)

Linux 7.3-rc7 (2026-10-12) as an opt-in dist-kernel; the existing
=7.3_rc* package.mask entry keeps covering it.

Pins unchanged (match ::gentoo 7.2.10): PATCHSET 7.1.9, CONFIG_VER 7.2.5-gentoo,
gentoo-kernel-config-g19. Verified with a local unprivileged `ebuild prepare`
(USE="-secureboot -modules-sign"): the rc7 diff and all 9 patches apply with no
rejects (0007 with fuzz 2); listnewconfig with the Fedora 7.2 config leaves 85
undecided symbols, up from 84 on rc6. Compile and boot not tested.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

commit 0c989fe0e51e1f1c3a940a50a1b8e3914ee0e94c
Author: lucascouts <lucascs@protonmail.com>
Date: Sun Oct 4 23:47:07 2026 -0300

up(sys-kernel/gentoo-kernel-7.3_rc5 -> 7.3_rc6, virtual/dist-kernel-7.3_rc5 -> 7.3_rc6), mod(metadata/md5-cache)

Linux 7.3-rc6 (2026-10-04) as an opt-in dist-kernel; the existing
=7.3_rc* package.mask entry keeps covering it.

Fix the -rc diff SRC_URI: it requested .../v7.3-rcN/7.2, which git.kernel.org
answers with 404. The base ref needs the "v" prefix (.../v7.3-rcN/v7.2), as in
kernel-2.eclass, which builds the same patch-$.patch for git-sources. The
rc5 ebuild only fetched because the distfile was already cached locally.

Pins unchanged (match ::gentoo 7.2.9): PATCHSET 7.1.9, CONFIG_VER 7.2.5-gentoo,
gentoo-kernel-config-g19. Verified with a local unprivileged `ebuild prepare`
(USE="-secureboot -modules-sign"): the rc6 diff and all 9 patches apply with no
rejects (0007 with fuzz 2); listnewconfig with the Fedora 7.2 config leaves 84
undecided symbols, up from 83 on rc5. Compile and boot not tested.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

commit 3891bc3343a992c8e9d97066911e5e2d427e7374
Author: lucascouts <lucascs@protonmail.com>
Date: Sun Oct 4 00:05:24 2026 -0300

kde-plasma/powerdevil, sys-kernel/gentoo-kernel, virtual/dist-kernel: drop copies ::gentoo caught up with

powerdevil-6.7.5-r3: ::gentoo ships the same brightness-slider fix (same
hunks, different patch name). gentoo-kernel-7.2.9 and dist-kernel-7.2.9:
byte-identical to ::gentoo. 6.7.91 and 7.3_rc5 stay. gentoo-kernel-bin-7.2.9
is kept as the base for its next mirror bump.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

commit c4e700a8f06332dd232da0636949ed49d1c7210b
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Oct 3 13:22:39 2026 -0300

add(sys-kernel/{gentoo-kernel,gentoo-kernel-bin}-7.2.9, virtual/dist-kernel-7.2.9, metadata/md5-cache/{sys-kernel/gentoo-kernel-7.2.9, sys-kernel/gentoo-kernel-bin-7.2.9, virtual/dist-kernel-7.2.9}), mod(sys-kernel/gentoo-kernel/Manifest)

Mirror the 7.2.9 dist-kernel ahead of ::gentoo (still at 7.2.8). Both
ebuilds are verbatim copies of the official 7.2.8 ones with only
SHA256SUM_DATE moved to 20261003. gentoo-kernel-bin is new to the
overlay: Gentoo already published the 7.2.9 binpkgs for amd64, arm64,
ppc64le and x86. virtual/dist-kernel follows because both PDEPEND on
>=virtual/dist-kernel-$.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

commit 726486dc139104081dc8d6c331f4f5c393d8e03a
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Oct 2 17:48:56 2026 -0300

add(sys-kernel/gentoo-kernel-7.3_rc5, virtual/dist-kernel-7.3_rc5), add(metadata/{md5-cache/sys-kernel/gentoo-kernel-7.3_rc5, md5-cache/virtual/dist-kernel-7.3_rc5}), mod(profiles/package.mask)

Ship Linux 7.3-rc5 as a dist-kernel, opt-in. ::gentoo never ships -rc
dist-kernels; its 7.3-rc kernels exist only as git-sources (sources, no
config, no initramfs, no module signing).

The ebuild is the official gentoo-kernel-7.2.8 with three -rc changes:

1. Source = linux-7.2.tar.xz + Linus's cumulative diff from git.kernel.org,
under the distfile name git-sources already uses. Its BLAKE2B matches
::gentoo's git-sources Manifest byte for byte; all 6 DIST entries are
identical to ::gentoo's, so nothing is self-hosted.
2. verify-sig is dropped: sha256sums.asc has no entry for an -rc. The four
axes this changes are tagged BENTOO-DIVERGENCE.
3. PATCH_PV is the series, so EXTRAVERSION is -rc5 and the release string is
7.3.0-rc5-gentoo-dist, which kernel-build checks against PV.

Both packages are package.mask'ed: 7.3_rc5 sorts above 7.2.x, so unmasked it
would move every ~arch user onto a release candidate.

Verified locally, without compiling the kernel:
- linux-gentoo-patches-7.1.9: 9/9 apply with zero rejects
- ebuild ... configure: PASS (unpack, rc diff, patchset, config merge,
olddefconfig, kernel-build's KV/PV check)
- emerge -pv: masked by package.mask; @world does not pull it; with the
unmask it resolves to a new slot + virtual + 4 module rebuilds
- nvidia-drivers-580.178.04, mt7927-dkms, asus-ec-sensors: all C objects
compile against 7.3-rc5 (link stage not proven without a full build)
- pkgcheck: only PythonCompatUpdate (inherited) and the known benign
NonexistentDeps on the virtual; gentoo-parity.sh: 4/4 JUSTIFIED

Not verified: kernel compile, module link, boot. The Fedora 7.2.5 config
leaves 83 symbols undecided on 7.3; most are new drivers that end up off.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

commit 180091b9cbf43dd4671b1fcec1e214fbe4bc4449
Author: lucascouts <lucascs@protonmail.com>
Date: Wed Sep 2 23:58:46 2026 -0300

del: drop 4 more packages ::gentoo has caught up to

thunderbird, thunderbird-l10n, gentoo-kernel and dist-kernel were removed from
the tree in a session that did not finish the job. This completes it and commits
the result.

The removals themselves are sound -- ::gentoo now ships the exact version each
one carried, so none of the four had anything left to add:

mail-client/thunderbird 155.0 ::gentoo max 155.0
mail-client/thunderbird-l10n 155.0 ::gentoo max 155.0
sys-kernel/gentoo-kernel 7.2.3 ::gentoo max 7.2.3
virtual/dist-kernel 7.2.3 ::gentoo max 7.2.3

What was missing was everything around the ebuilds. Four md5-cache entries were
left pointing at ebuilds that no longer exist, and the two .autoupdate records
were still live -- the probe would have kept reporting versions for packages the
tree does not have, and the applier would have tried to bump them. Neither shows
up in git status as a problem, which is exactly why a half-finished removal
survives: the part that rots is the part nothing renders.

Both records are disabled rather than deleted, per overlay convention, each
carrying its reason in disabled_by. gentoo-kernel and dist-kernel never had a
record -- they mirror ::gentoo's and track the patchset, not an upstream probe.

Verified against the checkout via PORTAGE_REPOSITORIES, without syncing:

emerge -puDN @world exit 0, no conflict, no mask
all four resolve to ::gentoo at the same version

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

commit bf259bab1073d4f7b33ffd1436f28ad40aa34218
Author: lucascouts <lucascs@protonmail.com>
Date: Wed Sep 2 12:36:56 2026 -0300

up(sys-kernel/gentoo-kernel-7.2.2 -> 7.2.3, virtual/dist-kernel-7.2.2 -> 7.2.3), del(sys-kernel/gentoo-kernel-7.2., virtual/dist-kernel-7.2. [superseded by ::gentoo])

::gentoo opened the 7.2 series on 2026-09-01 with gentoo-kernel-7.2.2, and its
ebuild supersedes every 7.2.x this overlay carried on all three axes that made
ours diverge: it uses the official linux-gentoo-patches-7.1.9 patchset, the
real 7.2.2 Fedora config, and a newer DEBIAN_COMMIT. Note what the first one
means -- the reuse of a previous-series patchset that bentoo bet on in August
is now upstream's own choice for 7.2, not an overlay-local workaround. Both
7.2.3 ebuilds are therefore verbatim copies of their ::gentoo 7.2.2
counterparts with PV bumped, and the self-hosted
linux-gentoo-patches-7.2.0-bentoo.tar.xz is no longer referenced by anything.

Total divergence from the official ebuild is one line, SHA256SUM_DATE=20260902.
virtual/dist-kernel-7.2.3 is byte-identical to the official one.

CONFIG_VER deliberately stays at 7.2.2-gentoo: the Fedora fork has no 7.2.3 tag
yet. Cost measured with `make listnewconfig` on the fully patched 7.2.3 tree
against the raw x86_64 Fedora config: 7 undecided symbols, and all 7 are the
CONFIG_GENTOO_* entries that patch 0008 creates and gentoo-kernel-config
resolves. Zero drift attributable to the config lag itself -- contrast the 69
symbols measured when the lag was a whole series (7.1.9 config on a 7.2 tree).

Verified, all locally:

patches the 9 patches of linux-gentoo-patches-7.1.9 apply in sequence to
the 7.2.3 tree with 0 rejects; 0007 takes fuzz 1, exactly as it
already did on 7.2.1 and 7.2.2
distfiles patch-7.2.3.xz matches the signed kernel.org sha256sums.asc; the
three shared distfiles match the ::gentoo Manifest by BLAKE2B
pkgcheck clean on both packages, except a PythonCompatUpdate notice
inherited verbatim from the official ebuild
parity gentoo-parity.sh: 0 UNDOCUMENTED, no axis diverges
resolution emerge -pv against the checkout resolves; the PDEPEND finds
virtual/dist-kernel-7.2.3 and 0 KiB needs downloading

NOT build-tested: this host has no sudo, so nothing was merged. What is proven
is that the patches apply and the config does not drift, not that the kernel
compiles.

Merging this will rebuild the four out-of-tree module packages that depend on
virtual/dist-kernel: nvidia-drivers, virtualbox-modules, mt7927-dkms and
asus-ec-sensors, all with modules-sign active.

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

commit f90e11560b26c7dace9eb6ab0f1c6ed0b7f998a8
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Aug 28 11:24:21 2026 -0300

add(sys-kernel/gentoo-kernel-7.2.2, virtual/dist-kernel-7.2.2), add(metadata/{md5-cache/sys-kernel/gentoo-kernel-7.2.2, md5-cache/virtual/dist-kernel-7.2.2})

kernel.org published 7.2.2 today. This is a plain point release: the only
functional edit against 7.2.1 is SHA256SUM_DATE, 20260827 -> 20260828, which
follows the last-modified of cdn.kernel.org's sha256sums.asc and only matters
under USE=verify-sig. Everything else in the diff is the header comment,
brought back in line with the facts re-measured for this bump.

::gentoo still has not opened the 7.2 series -- top dist-kernel is 7.1.11 --
so the self-hosted patchset stays, keeping the linux-gentoo-patches-7.2.0-bentoo
filename because the bytes are unchanged. Worth recording, because the comment
previously read as if this overlay were doing something unusual: reusing an
older patchset is what Gentoo itself does. The official 7.1.11 ebuild also
sets PATCHSET=linux-gentoo-patches-7.1.9; that tarball is simply the newest
one upstream has published, and patchsets/7.2/ and 7.1. are all 404.

CONFIG_VER still lags at 7.1.9-gentoo, and now with a source for why rather
than an assumption: git ls-remote on fork/fedora/kernel shows 7.1.9-gentoo is
still the newest tag. Re-measured the cost with `make listnewconfig` against
the raw Fedora x86_64 config on a 7.2.2 tree: 69 symbols undecided, 47 resolve
to n. Of the 22 that resolve to y/m, 18 are new KUNIT/self-test entries that
CONFIG_KUNIT_ALL_TESTS=m would enable under a 7.2 config too, leaving exactly
four substantive symbols -- SCHED_CACHE, KMALLOC_PARTITION_RANDOM,
CMA_SIZE_PERNUMA, NET_VENDOR_ALIBABA -- all at the upstream default. The
figure differs from the 88 recorded on 7.2.1 because that one was measured
after the gentoo config merge; this one measures the Fedora config alone,
which is the metric the 7.2.0 note defined.

Verified: src_unpack + src_prepare complete through the real ebuild ("Source
prepared."), tree at SUBLEVEL = 2, no .rej or .orig anywhere in the work tree;
all 9 patches applied via eapply, with 0007 taking fuzz exactly as it did on
7.2.1; the resulting distro/Kconfig is the full 307-line dist-kernel version
carrying the KSPP section, sourced from the root Kconfig, and `make
olddefconfig` yields CONFIG_GENTOO_LINUX, _UDEV, _PORTAGE, _INIT_SCRIPT and
_PRINT_FIRMWARE_INFO all =y. Portage validated every Manifest checksum
against the files on disk, and the sha256sums.asc entries for linux-7.2.tar.xz
and patch-7.2.2.xz match the bytes fetched. pkgcheck reports nothing new
(PythonCompatUpdate comes from kernel-build.eclass and is present on the
official ebuild too; NonexistentDeps on the virtual is the shape of its || ( )
block). emerge -pv resolves and schedules the four out-of-tree module
packages -- nvidia-drivers, virtualbox-modules, mt7927-dkms, asus-ec-sensors
-- for rebuild.

NOT verified: the kernel was neither compiled nor installed, and neither
Secure Boot signing nor module signing was exercised. This host has no sudo,
and both gates in kernel-build_pkg_setup need a root-owned private key
(/etc/portage/secureboot.pem and /etc/kernel/keys/module-signing.key), so the
prepare run above used USE="-secureboot -modules-sign". Neither flag changes
what src_prepare produces: secureboot only appends two fragments to
kernel-build_merge_configs, and modules-sign acts in src_install.

7.2.0 and 7.2.1 are both kept: 7.2.1 is the currently running kernel.

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

commit 7decc8b4c61a877f011f94baa3c6f33134c047fa
Author: lucascouts <lucascs@protonmail.com>
Date: Thu Aug 27 15:18:16 2026 -0300

add(sys-kernel/gentoo-kernel-7.2.1, virtual/dist-kernel-7.2.1), add(metadata/{md5-cache/sys-kernel/gentoo-kernel-7.2.1, md5-cache/virtual/dist-kernel-7.2.1})

kernel.org published 7.2.1 today, which removes the structural blocker the
7.2.0 ebuild had to work around: a .0 release has no incremental patch, so
that ebuild dropped patch-$.xz from SRC_URI along with its eapply
call and its verify-sig checksum entry. 7.2.1 has one, so all three are back
to their official form.

::gentoo still has not opened the 7.2 series (top dist-kernel is 7.1.10 and
patchsets/7.2/ does not exist), so the self-hosted patchset stays. It keeps
the linux-gentoo-patches-7.2.0-bentoo filename on purpose: the bytes are
unchanged, and a second name for identical content would only add a redundant
distfile. Re-verified for this bump -- all 9 patches apply to the 7.2.1 tree
in sequence with zero rejects, and the resulting distro/Kconfig is the full
307-line dist-kernel version, not the 170-line genpatches one.

CONFIG_VER still lags at 7.1.9-gentoo because Fedora has no 7.2 config. The
comment inherited from 7.2.0 claimed 62 undecided symbols; re-measured with
`make listnewconfig` on this tree it is 88, of which 61 resolve to n. Of the
27 that resolve to y/m, 14 are new KUNIT entries and 5 are CONFIG_GENTOO_*
that take their defaults from the patchset's own distro/Kconfig regardless of
the Fedora config's vintage, leaving ~8 substantive symbols at the upstream
default. The comment now carries the measured figures.

Verified: src_unpack + src_prepare complete through the real ebuild ("Source
prepared."), tree at SUBLEVEL = 1, no rejects; Manifest checksums match the
signed kernel.org sha256sums.asc; pkgcheck clean apart from findings already
present on 7.2.0; emerge -pv resolves and schedules the four out-of-tree
module packages for rebuild. NOT verified: the kernel was not compiled or
installed -- this host has no sudo and USE=secureboot needs to write
/etc/portage/secureboot.pem.

7.2.0 is kept deliberately: it is the currently running kernel.

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

commit 9de7e41c492ee3d32a7772ab2a41d983338e96a9
Author: lucascouts <lucascs@protonmail.com>
Date: Sun Aug 23 15:02:25 2026 -0300

add(sys-kernel/gentoo-kernel-7.2.0, virtual/dist-kernel-7.2.0), add(metadata/{md5-cache/sys-kernel/gentoo-kernel-7.2.0, md5-cache/virtual/dist-kernel-7.2.0})

Mirror the dist-kernel ahead of ::gentoo, which has not opened the 7.2 series
yet: its top dist-kernel is 7.1.9 and patchsets/7.2/ does not exist upstream.

Two deliberate divergences from the official ebuild, both to be REVERTED once
::gentoo publishes 7.2.1/7.2.2:

1. PATCHSET is self-hosted on distfiles.obentoo.org. It is the 7.1.9
dist-kernel patchset verbatim. Reuse is safe and was verified, not
assumed: all 9 patches apply in sequence to the 7.2 tree with zero
rejects, and the genpatches 7.1 and 7.2 branches are byte-identical
across their 11 base patches, so Gentoo wrote nothing new for 7.2.
The -bentoo suffix is deliberate -- the upstream name would collide
with the file Gentoo is about to publish, and a same-named distfile
already in DISTDIR does not get its DIST entry recalculated.

2. There is no patch-7.2.0.xz. kernel.org never publishes an incremental
patch for a .0 release, which is why Gentoo always opens a dist-kernel
series at .1/.2. The SRC_URI entry, the eapply call and the verify-sig
checksum entry are absent accordingly.

CONFIG_VER intentionally lags at 7.1.9-gentoo; Fedora has no 7.2 config yet.
Measured, not guessed: 62 symbols go undecided on a 7.2 tree and 45 resolve
to n, the remainder being mostly new KUNIT tests that CONFIG_KUNIT_ALL_TESTS=m
would enable under a 7.2 config too.

Verified: patches 9/9 in sequence, no rejects; all 5 distfiles check against
the Manifest; linux-7.2.tar.xz hashes match the gentoo-sources Manifest;
full src_compile succeeds (7.2.0-gentoo-dist, 24M bzImage, 4998 modules,
zero errors); gentoo-parity.sh exits 0. Not covered: the secureboot and
modules-sign paths, which need keys under /etc and root.

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

commit c87eaee98206cae92218e83297425ece479aafc4
Author: lucascouts <lucascs@protonmail.com>
Date: Sun Jul 26 09:28:43 2026 -0300

add(app-editors/zed-bin-1.13.0_pre), add(metadata/{md5-cache/app-editors/kiro-1.0.228, md5-cache/app-editors/zed-1.14.0_pre20260726, md5-cache/app-editors/zed-bin-1.13.0_pre, md5-cache/dev-util/antigravity-hub-bin-2.4.2.6711062033203200, md5-cache/dev-util/mesa_clc-26.2.0_pre20260726, md5-cache/media-libs/mesa-26.2.0_pre20260726, md5-cache/sci-ml/ik_llama-cpp-0_pre20260725, md5-cache/sci-ml/ollama-0.32.4}), del(sys-kernel/gentoo-kernel-7.1.5, virtual/dist-kernel-7.1.5), up(app-editors/{kiro-1.0.212 -> 1.0.228, zed-1.14.0_pre20260725 -> 1.14.0_pre20260726}, dev-util/{antigravity-hub-bin-2.3.1.5358163105546240 -> 2.4.2.6711062033203200, mesa_clc-26.2.0_pre20260725 -> 26.2.0_pre20260726}, media-libs/mesa-26.2.0_pre20260725 -> 26.2.0_pre20260726, sci-ml/{ik_llama-cpp-0_pre20260723 -> 0_pre20260725, ollama-0.32.3 -> 0.32.4})

commit 888215e0178ef7ae137e8ab3334f9836beb1e22c
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Jul 24 17:08:04 2026 -0300

add(sys-kernel/gentoo-kernel-7.1.5, virtual/dist-kernel-7.1.5), add(metadata/{md5-cache/sys-kernel/gentoo-kernel-7.1.5, md5-cache/virtual/dist-kernel-7.1.5})

Mirror do gentoo-kernel oficial adiantado à frente do Gentoo (que está no 7.1.4):
copia do 7.1.4 ::gentoo com PATCHSET=linux-gentoo-patches-7.1.5 e SHA256SUM_DATE=20260724.
virtual/dist-kernel-7.1.5 obrigatório (PDEPEND do gentoo-kernel).

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

commit dd77c3f99aff93987cf977d28419edb573e00e7a
Author: lucascouts <lucascs@protonmail.com>
Date: Tue Jun 2 00:54:39 2026 -0300

del(sys-kernel/gentoo-kernel-6.18.34)

commit 234e38ebd65c5c9cc5d59e0f9be5f9feae45bc2a
Author: lucascouts <lucascs@protonmail.com>
Date: Tue Jun 2 00:52:30 2026 -0300

add(app-editors/kiro-0.12.263, net-misc/postman-bin-12.12.6, sys-apps/pnpm-11.5.0, sys-kernel/gentoo-kernel-6.18.34), add(metadata/{md5-cache/app-editors/zed-1.6.0_pre20260602, md5-cache/dev-util/claude-code-2.1.160, md5-cache/dev-util/codex-0.136.0, md5-cache/sys-apps/pnpm-11.5.0, md5-cache/sys-kernel/gentoo-kernel-6.18.34}), mod(app-portage/bentoolkit-0.2.2), mod(metadata/md5-cache/dev-util/codex-0.135.0, .autoupdate/packages.toml), up(app-editors/zed-1.6.0_pre20260531 -> 1.6.0_pre20260602, dev-util/{claude-code-2.1.159 -> 2.1.160, codex-0.135.0 -> 0.136.0})

commit 1b11cbe46a1ee43eb5ec4c380afe740da8c9ce13
Author: lucascouts <lucascs@protonmail.com>
Date: Fri May 1 20:59:31 2026 -0300

del(sys-kernel/{gentoo-kernel-6.18.26, gentoo-kernel-7.0.3}, virtual/{dist-kernel-6.18.25, dist-kernel-6.18.26, dist-kernel-7.0.2, dist-kernel-7.0.3})

commit 00f478ca1f160986d84a108017e8c4e9306da489
Author: lucascouts <lucascs@protonmail.com>
Date: Thu Apr 30 19:14:03 2026 -0300

add(sys-kernel/{gentoo-kernel-6.18.26, gentoo-kernel-7.0.3}, virtual/{dist-kernel-6.18.25, dist-kernel-6.18.26, dist-kernel-7.0.2, dist-kernel-7.0.3})