Comment
The change is a straightforward source update in .SRCINFO: it bumps the XanMod patch from 7.2.13-xanmod1 to 7.2.14-xanmod1 and updates the corresponding SHA-256 checksum. No new sources, scripts, build steps, or privilege-related artifacts are introduced, and the remaining sources still use HTTPS and pinned checksums/PGP keys. Based on the diff alone, there are no security red flags beyond the usual trust in the upstream patch source.
@@ -25,13 +25,13 @@ pkgbase = linux-xanmod
options = !strip
source = https://cdn.kernel.org/pub/linux/kernel/v7.x/linux-7.2.tar.xz
source = https://cdn.kernel.org/pub/linux/kernel/v7.x/linux-7.2.tar.sign
- source = patch-7.2.13-xanmod1.xz::https://sourceforge.net/projects/xanmod/files/releases/main/7.2.13-xanmod1/patch-7.2.13-xanmod1.xz/download
+ source = patch-7.2.14-xanmod1.xz::https://sourceforge.net/projects/xanmod/files/releases/main/7.2.14-xanmod1/patch-7.2.14-xanmod1.xz/download
source = choose-gcc-optimization.sh
validpgpkeys = ABAF11C65A2970B130ABE3C479BE3E4300411886
validpgpkeys = 647F28654894E3BD457199BE38DBBDC86092693E
sha256sums = f9fef3d14c0df53819026f4be74459835c2a0b0dcbf5b5bbd9ea19f0829402b3
sha256sums = SKIP
- sha256sums = 1565392dcf546c8ebe329fa1229344ce790fdd404838e87ffacf329d10f044e3
+ sha256sums = 590e153d2f75049d4184a2eb76bb752813a6a768f75e60d7c725135f6a7338e5
sha256sums = f4acc1760990c54348a029315d1505ccb7c7270cd70a9aeb728bffcced51e767
pkgname = linux-xanmod