Review Results

Comment

The only change in this .SRCINFO hunk is a version bump from 7.1.4 to 7.1.5. No build logic, sources, checksums, install scripts, or permissions are changed in the reviewed diff. The existing HTTP homepage URL is a pre-existing metadata issue, but it is not introduced by this change and does not by itself indicate a new security regression in this commit.

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

Comment

The change only updates the XanMod patch source from 7.1.4 to 7.1.5 and refreshes its SHA-256 in .SRCINFO. The source remains an HTTPS download from the project’s SourceForge release page, and there are no new build-time execution paths, privilege changes, or packaging behavior changes in this diff. This looks like a routine version bump with integrity metadata updated accordingly.

@@ -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.4-xanmod1.xz::https://sourceforge.net/projects/xanmod/files/releases/main/7.1.4-xanmod1/patch-7.1.4-xanmod1.xz/download
+	source = patch-7.1.5-xanmod1.xz::https://sourceforge.net/projects/xanmod/files/releases/main/7.1.5-xanmod1/patch-7.1.5-xanmod1.xz/download
 	source = choose-gcc-optimization.sh
 	validpgpkeys = ABAF11C65A2970B130ABE3C479BE3E4300411886
 	validpgpkeys = 647F28654894E3BD457199BE38DBBDC86092693E
 	sha256sums = 691f44797fbe790dc8a321604c927087526ad27b6d649925d60f8eed0a2564a0
 	sha256sums = SKIP
-	sha256sums = 1faf52109691e82bd85296a778babd6d7d3b606a3d266db7a7c74d5b9afd58c7
+	sha256sums = 72f1fd755581ae24793c1d6a1721ea902172bebb89d2014977076595f6e059dc
 	sha256sums = f4acc1760990c54348a029315d1505ccb7c7270cd70a9aeb728bffcced51e767
 
 pkgname = linux-xanmod

Comment

This change only bumps the package version from 7.1.4 to 7.1.5 in PKGBUILD. No source URLs, checksums, build steps, install scripts, permissions, or packaging logic are modified. On its face this is a routine version update with no security-relevant behavior change visible in the provided diff.

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

Comment

The change only bumps the upstream kernel package version from 7.1.4 to 7.1.5 and updates the corresponding SHA-256 for the downloaded XanMod patch. I did not see any new sources, build-time network behavior, privilege escalation, or packaging logic changes. The source URLs remain HTTPS and pinned to the same upstream locations, and the diff does not alter install scripts, units, or execution paths. Risk is therefore minimal and limited to normal upstream content replacement verified by checksum.

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