Review Results

Comment

The change is a straightforward version bump in .SRCINFO: updated pkgver, kernel/header dependency versions, and the upstream source URL/checksum to the new OpenZFS release. The source remains HTTPS on the official GitHub release page, there are no new build-time commands, no added scripts, and no packaging/persistence red flags in this diff. Based on the provided hunk alone, this looks like routine metadata maintenance with low security risk.

@@ -1,14 +1,14 @@
 pkgbase = zfs-linux
-	pkgver = 2.4.3_7.0.14.arch1.1
+	pkgver = 2.4.4_7.1.8.arch1.3
 	pkgrel = 1
 	url = https://openzfs.org/
 	arch = x86_64
 	license = CDDL
-	makedepends = linux-headers=7.0.14.arch1-1
+	makedepends = linux-headers=7.1.8.arch1-3
 	depends = kmod
-	depends = zfs-utils=2.4.3
-	depends = linux=7.0.14.arch1-1
-	source = https://github.com/openzfs/zfs/releases/download/zfs-2.4.3/zfs-2.4.3.tar.gz
+	depends = zfs-utils=2.4.4
+	depends = linux=7.1.8.arch1-3
+	source = https://github.com/openzfs/zfs/releases/download/zfs-2.4.4/zfs-2.4.4.tar.gz
 	sha256sums = 1f08f2d154f5189b5f1382848a32667b3d34066145b474c49cd3d41a5fba59a7
 
 pkgname = zfs-linux

Comment

The change only bumps the packaged ZFS and kernel version pins in PKGBUILD. There are no new sources, no build-script changes, no added network fetches, and no install-time or privilege-related behavior introduced by this diff. From the provided hunk alone, this is a routine version update with no evident security impact.

@@ -20,9 +20,9 @@
 #
 pkgbase="zfs-linux"
 pkgname=("zfs-linux" "zfs-linux-headers")
-_zfsver="2.4.3"
-_kernelver="7.0.14.arch1-1"
-_kernelver_full="7.0.14.arch1-1"
+_zfsver="2.4.4"
+_kernelver="7.1.8.arch1-3"
+_kernelver_full="7.1.8.arch1-3"
 _extramodules="${_kernelver_full/.arch/-arch}"
 
 pkgver="${_zfsver}_$(echo ${_kernelver} | sed s/-/./g)"