linux-lts510
- Path: arch/adapted/linux-lts510
- Build failure during the 2026-07-07 “build all packages for x86_64”
private-repo release pass (see
repo_release_logs/adapted_linux-lts510.log).
- Same defect class as
gcc47 (see memory/gcc47.md): source=() (PKGBUILD
lines 18-27) lists 0004-depmod-remove-depmod_hack_needed.patch,
0005-kernel-5.10-depmod-disable-for-packaging.patch, and
linux-5.10.229-python3.patch, but only 0001-..., 0002-...
(commented out in source=(), see below), 0003-..., and no-ultra-zstd.patch
actually exist in the directory. makepkg fails at source retrieval:
0004-depmod-remove-depmod_hack_needed.patch was not found in the build
directory and is not a URL.
- Note
0002-reorganize-gimple-includes-for-GCC-13.patch is present on
disk but is commented out of source=() (line 23, with an OpenSUSE build
service URL as a comment) – so that one’s fine, just currently unused.
The real gap is 0004/0005/the python3 patch.
- Not fixed as part of the mass build pass – flagging only, same as
gcc47. Needs the three missing patch files restored/regenerated before
this package can build again.
- 2026-08-02: looked into restoring them. Unlike
gcc47 (where the
gap turned out to not matter – generated docs were deleted anyway),
these three are load-bearing: prepare() applies every source=()
entry ending in .patch generically via patch -Np1, so all three
are expected to actually change kernel behavior (depmod hack
removal, disabling an in-tree depmod invocation during
modules_install that would conflict with packaging’s own depmod
run, and a python2->python3 fix in some 5.10.229-era build script).
Their exact historical content isn’t recoverable anywhere in this
environment (not on disk, not in another package’s patch set), and
guessing at kernel-packaging patch content isn’t safe to fabricate
– a wrong depmod patch specifically risks breaking module loading
at boot, and there’s no way to verify correctness here short of a
full build + real boot test. Left unresolved; whoever picks this up
needs either the original patches or to write and boot-test new
ones deliberately, not a guess-based restoration.