Comment
The change only bumps the Spotify repository metadata filenames from release -1 to -2 in .SRCINFO. It does not introduce new sources, scripts, build steps, permissions changes, or package install behavior. The URLs remain the same HTTP endpoints as before, so this diff does not worsen the existing integrity concern, and there is no evidence in this change of malicious behavior or supply-chain manipulation beyond a routine upstream metadata refresh.
@@ -24,9 +25,9 @@ pkgbase = spotify
source = spotify.sh
source = spotify.protocol
source = LICENSE
- source = spotify-1.2.96.518-1-Release::http://repository.spotify.com/dists/testing/Release
- source = spotify-1.2.96.518-1-Release.sig::http://repository.spotify.com/dists/testing/Release.gpg
- source = spotify-1.2.96.518-1-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages
+ source = spotify-1.2.96.518-2-Release::http://repository.spotify.com/dists/testing/Release
+ source = spotify-1.2.96.518-2-Release.sig::http://repository.spotify.com/dists/testing/Release.gpg
+ source = spotify-1.2.96.518-2-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages
validpgpkeys = E1096BCBFF6D418796DE78515384CE82BA52C83A
sha512sums = 98d25bd748258ca8b8357313cd35c7188bb0b26ed2d4390b0208473aa9fa3491a095559762f8ba06ec0828d73e05ee8fb488f0f357340191da4c65dd1f93c519
sha512sums = da48b628a4ea925dd8521133ebf364b261b11aed252d264dde6605d915cdb631919ffe672c58534bcdb60869e5d87a49a60a8198780b99517123f0031e83fdb1