Review Results

Comment

The change only bumps the package metadata in .SRCINFO from 7.1.3.lqx2-2 to 7.1.3.lqx3-1. No build logic, sources, install scripts, or permissions are altered, and there are no new integrity or execution red flags in the provided diff. This appears to be a routine version/release update with no security impact visible from the change shown.

@@ -1,7 +1,7 @@
 pkgbase = linux-lqx
 	pkgdesc = Linux Liquorix
-	pkgver = 7.1.3.lqx2
-	pkgrel = 2
+	pkgver = 7.1.3.lqx3
+	pkgrel = 1
 	url = https://liquorix.net/
 	arch = x86_64
 	license = GPL-2.0-only

Comment

The change only bumps the liquourix-package source tarball from 7.1-3 to 7.1-4 and updates its checksum in .SRCINFO. The source remains an HTTPS GitHub archive from the same upstream project, with no new URLs, no build-script changes, and no evidence of added execution or privilege-related behavior in this diff. On its face this is a routine version refresh with integrity metadata updated accordingly.

@@ -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-3.tar.gz
+	source = https://github.com/damentz/liquorix-package/archive/7.1-4.tar.gz
 	validpgpkeys = ABAF11C65A2970B130ABE3C479BE3E4300411886
 	validpgpkeys = 647F28654894E3BD457199BE38DBBDC86092693E
 	sha512sums = d4d9c45261813559341c67ea53d4a47f5a04d1ad15e3c2b8222a09b5483380d2bfd31b8c675e144db2eb91f560d6cb28f66187a5ea4f24f6dfb82a4ad48064cc
 	sha512sums = SKIP
-	sha512sums = e7a8608cae766e372a07ae5543dd5caafda0f696eada99ea7393d8906b5dae28bd2fce2e888bf072cd57ad1216b3b2d2aef5e71ba50bdbc54c83349ddf166cfd
+	sha512sums = f906bc182f2d4aed81b7529b18b6fd81ac426d68602b18db1714baa52aac845ba3dd9b3dd50997a5dceb00d6bee7fe060d0d8b253cf89eb038994108f197a2da
 
 pkgname = linux-lqx
 	pkgdesc = The Linux Liquorix kernel and modules

Comment

The change only bumps the Liquorix patch release and pkgver/pkgrel, along with updating the expected sha512 for the upstream tarball. I did not see any new sources, build steps, install scripts, or privilege/network behavior introduced by this diff. The source URLs remain HTTPS and pinned to a specific archive release, and the change is consistent with a routine version refresh.

@@ -54,11 +54,11 @@ _htmldocs_enable=
 _major=7.1
 _srcname=linux-${_major}
 _lqxpatchname=liquorix-package
-_lqxpatchrel=3
+_lqxpatchrel=4
 _lqxpatchver=${_lqxpatchname}-${_major}-${_lqxpatchrel}
 pkgbase=linux-lqx
-pkgver=7.1.3.lqx2
-pkgrel=2
+pkgver=7.1.3.lqx3
+pkgrel=1
 pkgdesc='Linux Liquorix'
 url='https://liquorix.net/'
 arch=(x86_64)

Comment

The change only updates the recorded checksum for the Liquorix patch tarball and bumps the package version/release metadata accordingly. I did not find any new code execution, network fetches, privilege changes, install scripts, or other behavioral changes in the PKGBUILD diff. The source URLs remain HTTPS and pinned to a specific archive version, so this looks like a routine upstream refresh with no security impact evident from the diff alone.

@@ -106,7 +106,7 @@ validpgpkeys=(
 )
 sha512sums=('d4d9c45261813559341c67ea53d4a47f5a04d1ad15e3c2b8222a09b5483380d2bfd31b8c675e144db2eb91f560d6cb28f66187a5ea4f24f6dfb82a4ad48064cc'
             'SKIP'
-            'e7a8608cae766e372a07ae5543dd5caafda0f696eada99ea7393d8906b5dae28bd2fce2e888bf072cd57ad1216b3b2d2aef5e71ba50bdbc54c83349ddf166cfd')
+            'f906bc182f2d4aed81b7529b18b6fd81ac426d68602b18db1714baa52aac845ba3dd9b3dd50997a5dceb00d6bee7fe060d0d8b253cf89eb038994108f197a2da')