Review Results

Comment

The only change in this diff is a version bump in .SRCINFO from 7.1.10 to 7.1.11. No build logic, sources, checksums, install scripts, or packaging metadata beyond the version string changed. While the package URL still uses HTTP in the unchanged metadata, that is not introduced by this commit and does not affect the reviewed delta. No security issue is evident in this change alone.

@@ -1,6 +1,6 @@
 pkgbase = linux-xanmod
 	pkgdesc = Linux Xanmod - Stable Mainline [MAIN]
-	pkgver = 7.1.10
+	pkgver = 7.1.11
 	pkgrel = 1
 	url = http://www.xanmod.org/
 	arch = x86_64

Comment

The change is a straightforward source-version bump in .SRCINFO: it updates the XanMod patch URL from 7.1.10 to 7.1.11 and refreshes the corresponding SHA-256. No new sources, scripts, privileges, install hooks, or packaging behavior are introduced. The remaining sources are unchanged and use HTTPS. Based on the diff alone, this is low risk.

@@ -20,13 +20,13 @@ pkgbase = linux-xanmod
 	options = !strip
 	source = https://cdn.kernel.org/pub/linux/kernel/v7.x/linux-7.1.tar.xz
 	source = https://cdn.kernel.org/pub/linux/kernel/v7.x/linux-7.1.tar.sign
-	source = patch-7.1.10-xanmod1.xz::https://sourceforge.net/projects/xanmod/files/releases/main/7.1.10-xanmod1/patch-7.1.10-xanmod1.xz/download
+	source = patch-7.1.11-xanmod1.xz::https://sourceforge.net/projects/xanmod/files/releases/main/7.1.11-xanmod1/patch-7.1.11-xanmod1.xz/download
 	source = choose-gcc-optimization.sh
 	validpgpkeys = ABAF11C65A2970B130ABE3C479BE3E4300411886
 	validpgpkeys = 647F28654894E3BD457199BE38DBBDC86092693E
 	sha256sums = 691f44797fbe790dc8a321604c927087526ad27b6d649925d60f8eed0a2564a0
 	sha256sums = SKIP
-	sha256sums = 0fdab87e24d5daf7c877e1e9422450c92e5a60301f47f3ca0550e8818d9562d2
+	sha256sums = 1e321710e16f2eba6696396546d30ec8f1de6f226a4aa22f2749a19d103b9cd3
 	sha256sums = f4acc1760990c54348a029315d1505ccb7c7270cd70a9aeb728bffcced51e767
 
 pkgname = linux-xanmod

Comment

The change is a trivial version bump in PKGBUILD from 7.1.10 to 7.1.11 with no alteration to sources, build steps, install scripts, permissions, or package metadata beyond pkgver. I do not see any new supply-chain, privilege, or persistence risk introduced by this diff alone.

@@ -73,7 +73,7 @@ fi
 
 pkgbase=linux-xanmod
 _major=7.1
-pkgver=${_major}.10
+pkgver=${_major}.11
 _branch=7.x
 xanmod=1
 _revision=

Comment

The change only updates a sha256 checksum for one existing source artifact in PKGBUILD. I did not see any new sources, build steps, network fetches, privilege changes, or packaging logic changes in the provided hunk. This is a low-risk integrity update, likely reflecting an upstream source refresh or repackaging of an already-declared file. No direct security issue is evident from this diff alone.

@@ -120,7 +120,7 @@ done
 
 sha256sums=('691f44797fbe790dc8a321604c927087526ad27b6d649925d60f8eed0a2564a0'
             'SKIP'
-            '0fdab87e24d5daf7c877e1e9422450c92e5a60301f47f3ca0550e8818d9562d2'
+            '1e321710e16f2eba6696396546d30ec8f1de6f226a4aa22f2749a19d103b9cd3'
             'f4acc1760990c54348a029315d1505ccb7c7270cd70a9aeb728bffcced51e767')
 
 export KBUILD_BUILD_HOST=${KBUILD_BUILD_HOST:-archlinux}