Review Results

Comment

The change only bumps pkgver in .SRCINFO from 7.2.9.lqx2 to 7.2.10.lqx1. No sources, checksums, build steps, install scripts, or permissions are modified, and there are no new network, privilege, or persistence concerns visible in this diff. This is a routine metadata/version update with negligible security impact.

@@ -1,6 +1,6 @@
 pkgbase = linux-lqx
 	pkgdesc = Linux Liquorix
-	pkgver = 7.2.9.lqx2
+	pkgver = 7.2.10.lqx1
 	pkgrel = 1
 	url = https://liquorix.net/
 	arch = x86_64

Comment

The change is a straightforward source version bump in .SRCINFO from liquorix-package 7.2-16 to 7.2-17, with the corresponding checksum update. The upstream source remains the same GitHub repository, uses HTTPS, and there are no new build steps, scripts, binaries, or privilege-related artifacts introduced by this diff. No security red flags are evident from this metadata-only update.

@@ -23,12 +23,12 @@ pkgbase = linux-lqx
 	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 = https://github.com/damentz/liquorix-package/archive/7.2-16.tar.gz
+	source = https://github.com/damentz/liquorix-package/archive/7.2-17.tar.gz
 	validpgpkeys = ABAF11C65A2970B130ABE3C479BE3E4300411886
 	validpgpkeys = 647F28654894E3BD457199BE38DBBDC86092693E
 	sha512sums = 47e63679363261a864d271277340a6f2d45f544e1a056be4159df081f4f6537d0efa865c4af26611ab33a3079ee65db88ec2f6bc0e5fff43e0c043cde0cd91e1
 	sha512sums = SKIP
-	sha512sums = 72db225f1f0efa39f607022cbec2551d3d2930b8dc61c7999200216b3a23c46a80ad487bba8a3e90f6721b5c95b777a7f61ea8982a1843c3cd4caf4d84d71d67
+	sha512sums = 5266d8d57bb8c7bdb61b310cf54569d9267140d65bff61d5d21e89ee7789aaf1b74993339adfb382c7064b42c485e870a4309ef1d488b70e974a2475da8bfdf3
 
 pkgname = linux-lqx
 	pkgdesc = The Linux Liquorix kernel and modules

Comment

The change is a routine version bump in PKGBUILD: it updates the Liquorix patch release number, kernel package version, and the corresponding SHA-512 checksum for the new upstream tarball. The source URLs remain HTTPS and pinned to a specific release archive, there are no new build-time commands, no new install scripts, and no packaging/persistence red flags introduced by this diff. Risk is therefore minimal.

@@ -54,10 +54,10 @@ _htmldocs_enable=
 _major=7.2
 _srcname=linux-${_major}
 _lqxpatchname=liquorix-package
-_lqxpatchrel=16
+_lqxpatchrel=17
 _lqxpatchver=${_lqxpatchname}-${_major}-${_lqxpatchrel}
 pkgbase=linux-lqx
-pkgver=7.2.9.lqx2
+pkgver=7.2.10.lqx1
 pkgrel=1
 pkgdesc='Linux Liquorix'
 url='https://liquorix.net/'

Comment

The change is limited to a version bump and an updated sha512 checksum for the upstream source tarball/patch. I do not see any new code execution, network fetches outside the existing source array, privilege changes, install-script behavior, or packaging policy violations introduced by this diff. The only security-relevant question is whether the new checksum matches the intended upstream release, but that is a normal integrity update rather than a red flag in the diff itself.

@@ -106,7 +106,7 @@ validpgpkeys=(
 )
 sha512sums=('47e63679363261a864d271277340a6f2d45f544e1a056be4159df081f4f6537d0efa865c4af26611ab33a3079ee65db88ec2f6bc0e5fff43e0c043cde0cd91e1'
             'SKIP'
-            '72db225f1f0efa39f607022cbec2551d3d2930b8dc61c7999200216b3a23c46a80ad487bba8a3e90f6721b5c95b777a7f61ea8982a1843c3cd4caf4d84d71d67')
+            '5266d8d57bb8c7bdb61b310cf54569d9267140d65bff61d5d21e89ee7789aaf1b74993339adfb382c7064b42c485e870a4309ef1d488b70e974a2475da8bfdf3')