Version #2061 of linux-lqx · commit 671c5866c3e1 · status Reviewed
The change only bumps pkgver in .SRCINFO from 7.1.8.lqx2 to 7.1.8.lqx3. This is metadata-only and does not alter sources, build steps, install scripts, permissions, or any runtime behavior. No security-relevant red flags are introduced by this diff alone.
@@ -1,6 +1,6 @@
pkgbase = linux-lqx
pkgdesc = Linux Liquorix
- pkgver = 7.1.8.lqx2
+ pkgver = 7.1.8.lqx3
pkgrel = 1
url = https://liquorix.net/
arch = x86_64
The change is a straightforward version bump in .SRCINFO for the AUR metadata: the upstream GitHub archive moved from 7.1-11 to 7.1-12 and the corresponding checksum was updated. The source remains the same official upstream repository, over HTTPS, with no new sources, scripts, build steps, or privilege-related artifacts introduced. No security-relevant behavior changes are visible in this 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-11.tar.gz
+ source = https://github.com/damentz/liquorix-package/archive/7.1-12.tar.gz
validpgpkeys = ABAF11C65A2970B130ABE3C479BE3E4300411886
validpgpkeys = 647F28654894E3BD457199BE38DBBDC86092693E
sha512sums = d4d9c45261813559341c67ea53d4a47f5a04d1ad15e3c2b8222a09b5483380d2bfd31b8c675e144db2eb91f560d6cb28f66187a5ea4f24f6dfb82a4ad48064cc
sha512sums = SKIP
- sha512sums = 8df77b747541b671b9599b023a8c2b4a22027a22c89b9c2832f59add798400e3dc1b01f670fd6066c84a1e53441456e8d3cd863f0bc60f3f94a68e9de1505b86
+ sha512sums = c42c878fd07fb3ea761da38c9130aaa40863c13671eb9786a8b6ef9dce5614c01e1deba41681c4ab8ddffe9ae38d2f1535454917f446fa04ef460f8f4a88c1c8
pkgname = linux-lqx
pkgdesc = The Linux Liquorix kernel and modules
The change is a simple version bump in PKGBUILD metadata: _lqxpatchrel 11->12 and pkgver 7.1.8.lqx2->7.1.8.lqx3. No build logic, source URLs, checksums, install scripts, permissions, or package contents are altered in the provided diff. Based on this hunk alone there is no evidence of supply-chain risk or malicious behavior.
@@ -54,10 +54,10 @@ _htmldocs_enable=
_major=7.1
_srcname=linux-${_major}
_lqxpatchname=liquorix-package
-_lqxpatchrel=11
+_lqxpatchrel=12
_lqxpatchver=${_lqxpatchname}-${_major}-${_lqxpatchrel}
pkgbase=linux-lqx
-pkgver=7.1.8.lqx2
+pkgver=7.1.8.lqx3
pkgrel=1
pkgdesc='Linux Liquorix'
url='https://liquorix.net/'
The change only updates the package version and the SHA-512 checksum for the upstream Liquorix patch tarball, along with the corresponding patch release number. I did not find any new sources, build steps, privilege changes, or install-time behavior introduced by this diff. This is a routine integrity pin update, with no security red flags in the reviewed hunk.
@@ -106,7 +106,7 @@ validpgpkeys=(
)
sha512sums=('d4d9c45261813559341c67ea53d4a47f5a04d1ad15e3c2b8222a09b5483380d2bfd31b8c675e144db2eb91f560d6cb28f66187a5ea4f24f6dfb82a4ad48064cc'
'SKIP'
- '8df77b747541b671b9599b023a8c2b4a22027a22c89b9c2832f59add798400e3dc1b01f670fd6066c84a1e53441456e8d3cd863f0bc60f3f94a68e9de1505b86')
+ 'c42c878fd07fb3ea761da38c9130aaa40863c13671eb9786a8b6ef9dce5614c01e1deba41681c4ab8ddffe9ae38d2f1535454917f446fa04ef460f8f4a88c1c8')