Review Results

Comment

The only change in this .SRCINFO hunk is a version bump from 21.0.4 to 21.1. No build logic, sources, install scripts, permissions, or package metadata beyond the version number are altered in the provided diff. On its face this is a routine upstream version update with no direct security red flags in the reviewed change.

@@ -1,6 +1,6 @@
 pkgbase = davinci-resolve
 	pkgdesc = Professional A/V post-production software suite from Blackmagic Design
-	pkgver = 21.0.4
+	pkgver = 21.1
 	pkgrel = 1
 	url = https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion
 	install = davinci-resolve.install

Comment

The change is a straightforward version bump in .SRCINFO: it updates pkgver and the local file:// source filename plus its SHA-256 checksum. There are no new sources, no network fetches, no script changes, and no packaging logic changes visible in this diff. The only security-relevant consideration is that the package now points to a different upstream release artifact, but the source remains a local file reference with an updated checksum, so integrity is preserved within the reviewed change.

@@ -31,9 +31,9 @@ pkgbase = davinci-resolve
 	conflicts = davinci-resolve-beta
 	conflicts = davinci-resolve-studio-beta
 	options = !strip
-	source = file://DaVinci_Resolve_21.0.4_Linux.zip
+	source = file://DaVinci_Resolve_21.1_Linux.zip
 	source = davinci-control-panels-setup.sh
-	sha256sums = d0bbc5bc09aaecaa693e22b2a037f42da8c984a5e9f3e1ff77c7db681325b50f
+	sha256sums = 4133e2c38072758a93e9a959504c251178134040096edad79cf0e87813019a2b
 	sha256sums = f17236fd68cead727c647bc31404e402922cdd491df5526f4b62364cbef9d3b8
 
 pkgname = davinci-resolve

Comment

The change is a straightforward version bump from 21.0.4 to 21.1 with corresponding checksum and internal path updates. I did not see any new execution paths, network access, privilege escalation, persistence mechanisms, or suspicious packaging behavior introduced by this diff. The added directory creation in package() only prepares expected install locations under $pkgdir, and the updated libglib/libgio version suffixes appear to be routine upstream bundle changes. Overall this looks low risk.

@@ -12,7 +12,7 @@
 
 _pkgname=resolve
 pkgname=davinci-resolve
-pkgver=21.0.4
+pkgver=21.1
 pkgrel=1
 pkgdesc='Professional A/V post-production software suite from Blackmagic Design'
 arch=('x86_64')

Comment

The change is limited to updating the package version/checksum and adding a few directory creations in package(). I do not see any new network fetches, command execution, privilege escalation, or persistence mechanisms. The new directories are under ${pkgdir}/opt/${_pkgname}, so they stay within the package staging area. The checksum update is expected for the new upstream release, and the rest of the diff is consistent with packaging adjustments for additional shipped content. No obvious security issues in this hunk.

@@ -26,7 +26,7 @@ makedepends=('libarchive' 'xdg-user-dirs' 'patchelf')
 conflicts=('davinci-resolve-studio' 'davinci-resolve-beta' 'davinci-resolve-studio-beta')
 source=("file://DaVinci_Resolve_${pkgver}_Linux.zip"
         "davinci-control-panels-setup.sh")
-sha256sums=('d0bbc5bc09aaecaa693e22b2a037f42da8c984a5e9f3e1ff77c7db681325b50f'
+sha256sums=('4133e2c38072758a93e9a959504c251178134040096edad79cf0e87813019a2b'
             'f17236fd68cead727c647bc31404e402922cdd491df5526f4b62364cbef9d3b8')
 install="${pkgname}.install"
 options=('!strip')

Comment

The change is a narrow versioned filename update in a cleanup rm command, replacing libglib/libgio/libgmodule/libgobject soname suffixes from .6800.4 to .8200.4. This does not introduce new execution paths, network access, privilege changes, or packaging destinations. It appears to be a maintenance fix for an upstream bundle version change, with no security-relevant behavior added in the diff hunk.

@@ -84,10 +84,10 @@ prepare() {
     sed -i "s|RESOLVE_INSTALL_LOCATION|/opt/${_pkgname}|g" "${_file}"
   done < <(find . -type f '(' -name "*.desktop" -o -name "*.directory" -o -name "*.directory" -o -name "*.menu" ')' -print0)
 
-  rm squashfs-root/libs/libglib-2.0.so.0{,.6800.4} \
-     squashfs-root/libs/libgio-2.0.so.0{,.6800.4} \
-     squashfs-root/libs/libgmodule-2.0.so.0{,.6800.4} \
-     squashfs-root/libs/libgobject-2.0.so.0{,.6800.4} \
+  rm squashfs-root/libs/libglib-2.0.so.0{,.8200.4} \
+     squashfs-root/libs/libgio-2.0.so.0{,.8200.4} \
+     squashfs-root/libs/libgmodule-2.0.so.0{,.8200.4} \
+     squashfs-root/libs/libgobject-2.0.so.0{,.8200.4} \
      squashfs-root/libs/libc++.so.1{,.0} \
      squashfs-root/libs/libc++abi.so.1{,.0}
   ln -s "../BlackmagicRAWPlayer/BlackmagicRawAPI" "squashfs-root/bin/"

Comment

The change only adds three empty directories under /opt/resolve during package() and does not introduce new execution paths, network access, privilege escalation, or persistence mechanisms. The rest of the diff is a version bump and checksum/library-name updates for the upstream installer contents. I do not see any security-relevant behavior in this hunk.

@@ -130,6 +130,9 @@ package() {
     "share/default_cm_config.bin"
   install -d -m 0755 "${pkgdir}/opt/${_pkgname}/.license"
   install -d -m 0755 "${pkgdir}/opt/${_pkgname}/Apple Immersive/Calibration"
+  install -d -m 0755 "${pkgdir}/opt/${_pkgname}/Extras"
+  install -d -m 0755 "${pkgdir}/opt/${_pkgname}/Fairlight"
+  install -d -m 0755 "${pkgdir}/opt/${_pkgname}/Immersive/Canon/STMap"
   # Install licenses
   install -d -m 0644 "${pkgdir}/usr/share/licenses/${pkgname}"
   ln -s "/opt/resolve/docs/License.html" "${pkgdir}/usr/share/licenses/${pkgname}"