Review Results

Comment

The only change in this .SRCINFO hunk is a package version bump from 7.1.12.lqx1 to 7.1.12.lqx2. There are no changes to source URLs, checksums, build steps, install scripts, dependencies, or packaging behavior. On its face this is a routine metadata update with no security-relevant indicators in the provided diff.

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

Comment

The change only bumps the liquorix-package source tarball from 7.1-20 to 7.1-21 and updates its checksum in .SRCINFO. The source remains on the official GitHub repository over HTTPS, and there are no new build steps, scripts, or integrity red flags introduced by this metadata-only update. No evidence of malicious behavior in the provided diff.

@@ -23,12 +23,12 @@ pkgbase = linux-lqx
 	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 = https://github.com/damentz/liquorix-package/archive/7.1-20.tar.gz
+	source = https://github.com/damentz/liquorix-package/archive/7.1-21.tar.gz
 	validpgpkeys = ABAF11C65A2970B130ABE3C479BE3E4300411886
 	validpgpkeys = 647F28654894E3BD457199BE38DBBDC86092693E
 	sha512sums = d4d9c45261813559341c67ea53d4a47f5a04d1ad15e3c2b8222a09b5483380d2bfd31b8c675e144db2eb91f560d6cb28f66187a5ea4f24f6dfb82a4ad48064cc
 	sha512sums = SKIP
-	sha512sums = 70f1060045cc14886e4ece5a1245ff2cf102c09fecb6d44acabab17171b0baa722ee4a67a8c7dafa9bbd4b39b4b4374942cd0aef0888cb46c444a4f250ec6222
+	sha512sums = 2dfaf80c27c33b8efe6930eef95abc8b0daf8cedb58dc8fe7686d1d669e10f6635bba68835af2f4c7692e482f6f96daddb11cb2c9f8a3ce09462472e9cb740d5
 
 pkgname = linux-lqx
 	pkgdesc = The Linux Liquorix kernel and modules

Comment

The change only bumps the Liquorix patch release from 20 to 21 and the package version from 7.1.12.lqx1 to 7.1.12.lqx2. No new sources, build steps, install scripts, permissions, or network-fetching behavior are introduced in the provided diff. This looks like a routine version update with no security-relevant changes in the reviewed hunk.

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

Comment

The change only updates the recorded SHA-512 checksum for the Liquorix patch tarball after bumping the patch release from 20 to 21 and pkgver from lqx1 to lqx2. The source remains an HTTPS GitHub archive under the expected upstream project, and there are no new build commands, network fetches, privilege changes, or packaging behavior changes in this diff. On its face this is a routine integrity update, not a security concern.

@@ -106,7 +106,7 @@ validpgpkeys=(
 )
 sha512sums=('d4d9c45261813559341c67ea53d4a47f5a04d1ad15e3c2b8222a09b5483380d2bfd31b8c675e144db2eb91f560d6cb28f66187a5ea4f24f6dfb82a4ad48064cc'
             'SKIP'
-            '70f1060045cc14886e4ece5a1245ff2cf102c09fecb6d44acabab17171b0baa722ee4a67a8c7dafa9bbd4b39b4b4374942cd0aef0888cb46c444a4f250ec6222')
+            '2dfaf80c27c33b8efe6930eef95abc8b0daf8cedb58dc8fe7686d1d669e10f6635bba68835af2f4c7692e482f6f96daddb11cb2c9f8a3ce09462472e9cb740d5')