Review Results

Comment

The change only bumps the package version in .SRCINFO from GE_Proton11_8 to GE_Proton11_9. No sources, checksums, build logic, install scripts, permissions, or systemd-related artifacts are modified in the reviewed diff. This is a routine metadata update with no apparent security impact.

@@ -1,6 +1,6 @@
 pkgbase = proton-ge-custom-bin
 	pkgdesc = A fancy custom distribution of Valves Proton with various patches
-	pkgver = GE_Proton11_8
+	pkgver = GE_Proton11_9
 	pkgrel = 1
 	epoch = 1
 	url = https://github.com/GloriousEggroll/proton-ge-custom

Comment

This is a metadata-only .SRCINFO update changing the provided version from GE.Proton11_8 to GE.Proton11_9. It does not introduce new sources, build steps, install scripts, permissions changes, or other executable content. The change is consistent with a package version bump and does not present an apparent security risk on its own.

@@ -28,7 +28,7 @@ pkgbase = proton-ge-custom-bin
 	optdepends = lapack: Vosk speech recognition support
 	optdepends = lib32-lapack: Vosk speech recognition support for 32bit applications
 	provides = proton
-	provides = proton-ge-custom=GE.Proton11_8
+	provides = proton-ge-custom=GE.Proton11_9
 	conflicts = proton-ge-custom
 	conflicts = proton-ge-bin
 	options = !strip

Comment

The change only updates the package to a newer upstream release tarball on GitHub and refreshes the corresponding SHA-512 checksums for x86_64 and aarch64. The source remains HTTPS from the expected upstream project, there are no new build-time commands, scripts, or privilege-related changes in this diff, and the integrity pins are preserved via updated checksums. No security issue is evident from this .SRCINFO-only version bump.

@@ -40,9 +40,9 @@ pkgbase = proton-ge-custom-bin
 	sha512sums = 5d1a841d3f8f65f9e62742f84eeccfb198a0292a97ba9109f377a550a4de0e2913d1e17b3d90ecd37ac09411dc67e54662dc1be301554ce05fd128d842252deb
 	sha512sums = 78ede6d50f9c43407da511c8b37dcf60aae2ddbd461c0081f0d0ce3de08ace3a84dee86e9253acbac829b47c5818ef4e1a354ccb05feaa9853ce279dc3f903fd
 	sha512sums = 60bcb1ad899d108fca9c6267321d11871feae96b696e44607ef533becc6decb493e93cbe699382e8163ad83f35cfa003a059499c37278f31afeba4700be6e356
-	source_x86_64 = GE-Proton11-8_1-x86_64.tar.gz::https://github.com/GloriousEggroll/proton-ge-custom/releases/download/GE-Proton11-8/GE-Proton11-8-x86_64.tar.gz
-	sha512sums_x86_64 = 180906415f91bd3f5228bf4d89e4bacd3021805ff8444bdc37eaa510bc19b90c73c366e2ba7d9a7338aee98965fec764b6d9f8449dda6b7bc80e9ceb83c793d4
-	source_aarch64 = GE-Proton11-8_1-aarch64.tar.gz::https://github.com/GloriousEggroll/proton-ge-custom/releases/download/GE-Proton11-8/GE-Proton11-8-aarch64.tar.gz
-	sha512sums_aarch64 = 04561208a7b64bd7a154fb162a60d346304db995b101a7c89b06d29abfb86ff87408e3d5192f305d151d8e2b92318b7a36f78d8039721730ba8f3974fd43c55e
+	source_x86_64 = GE-Proton11-9_1-x86_64.tar.gz::https://github.com/GloriousEggroll/proton-ge-custom/releases/download/GE-Proton11-9/GE-Proton11-9-x86_64.tar.gz
+	sha512sums_x86_64 = 30160946a5e4ffdf1f29d6f83a3d27108f6aa71b6aa59095b2c2260fe3a003b62acf8fdcb02a3dfc602b28473f5679d8a3eaee5a8adb141c1dfa01c42888da2d
+	source_aarch64 = GE-Proton11-9_1-aarch64.tar.gz::https://github.com/GloriousEggroll/proton-ge-custom/releases/download/GE-Proton11-9/GE-Proton11-9-aarch64.tar.gz
+	sha512sums_aarch64 = 80739cb28d68d946b55f00cabf228c5fae2201d90cc4d37728cefc851c9c23ab37ca2118883b21a9f58490832bdc1b12e2a2a0995dbbf1735716ac9da0bccfee
 
 pkgname = proton-ge-custom-bin

Comment

This change only bumps the package version from GE_Proton11_8 to GE_Proton11_9 and updates the corresponding SHA-512 checksums for the x86_64 and aarch64 source archives. No build logic, install scripts, permissions, or source URLs are changed, and there are no new network fetches or execution paths introduced by the diff. The risk is therefore minimal and limited to the usual trust in the upstream release artifact already pinned by checksum.

@@ -8,7 +8,7 @@
 ## pkginfo
 pkgdesc='A fancy custom distribution of Valves Proton with various patches'
 pkgname=proton-ge-custom-bin
-pkgver=GE_Proton11_8
+pkgver=GE_Proton11_9
 pkgrel=1
 epoch=1
 arch=('x86_64' 'aarch64')

Comment

The change is a routine version bump in a binary package: pkgver advances from GE_Proton11_8 to GE_Proton11_9 and the architecture-specific sha512 checksums are updated accordingly. I do not see any new sources, build-time network access, script execution, privilege escalation, or packaging behavior changes in the provided diff. Risk is low because the trust boundary remains the upstream release artifact, and the only security-relevant control here is the checksum pinning, which was updated consistently with the new version.

@@ -78,11 +78,11 @@ sha512sums=(
 )
 
 sha512sums_x86_64=(
-  '7757dc3c84f876d6cd18a060a97cfa50f8c5501c93ecb4bd909f3ad6dd9fa899f402fdb41361fd0a7e705427bed78abff0033b5e17aed9a3adaa8e74c579bd0c'
+  '30160946a5e4ffdf1f29d6f83a3d27108f6aa71b6aa59095b2c2260fe3a003b62acf8fdcb02a3dfc602b28473f5679d8a3eaee5a8adb141c1dfa01c42888da2d'
 )
 
 sha512sums_aarch64=(
-  '04561208a7b64bd7a154fb162a60d346304db995b101a7c89b06d29abfb86ff87408e3d5192f305d151d8e2b92318b7a36f78d8039721730ba8f3974fd43c55e'
+  '80739cb28d68d946b55f00cabf228c5fae2201d90cc4d37728cefc851c9c23ab37ca2118883b21a9f58490832bdc1b12e2a2a0995dbbf1735716ac9da0bccfee'
 )
 
 build() {