Looks like the underlying Packages file changed -- the following patch builds for me (making the PKGBUILD reflect the actual Packages file):
diff --git a/PKGBUILD b/PKGBUILD
index 4333fe7..7c2cc03 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -6,9 +6,9 @@
# Contributor: Eothred <yngve.levinsen@gmail.com>
pkgname=spotify
-pkgver='1.2.92.147'
+pkgver='1.2.95.453'
epoch=1
-_commit=g5b8f9367
+_commit=g0eeebbed
pkgrel=1
pkgdesc='A proprietary music streaming service'
arch=('x86_64')
@@ -34,7 +34,7 @@ source=("${pkgname}-${pkgver}-${_commit}-x86_64.deb::http://repository.spotify.c
"${pkgname}-${pkgver}-${pkgrel}-Release::http://repository.spotify.com/dists/testing/Release"
"${pkgname}-${pkgver}-${pkgrel}-Release.sig::http://repository.spotify.com/dists/testing/Release.gpg"
"${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages")
-sha512sums=('e84afeaa3c011c7e06cffa31d0a0113f8851bad57fc26317c2eef74b89985848bdd25b72e4f9a9e55948b8b927f3205a8b9c1047e2f28eec500ac7a2d4913cad'
+sha512sums=('902d9b8200d67e10a19ce5e34316ea14ed05e935fe5493c21f7a8db31b2ffc91375dd18a68734e781b815d57ac9e3aff36da79bce9ff6882a1f247542caab451'
'da48b628a4ea925dd8521133ebf364b261b11aed252d264dde6605d915cdb631919ffe672c58534bcdb60869e5d87a49a60a8198780b99517123f0031e83fdb1'
'999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
'2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
Pinned Comments
Antiz commented on 2025-11-23 18:37 (UTC) (edited on 2025-11-23 18:41 (UTC) by Antiz)
Please make sure to import the correct OpenPGP key first:
And always build in a clean chroot. It is as easy as:
It is expected that the package will break now and then, as spotify continuously changes download binaries, OpenPGP keys, etc (which is not appropriate, but we cannot change this). Please be patient if an update does not occur the next day, you can still use an existing spotify install or update the version yourself.
Antiz commented on 2023-09-13 13:21 (UTC)
@lightofpast Just pushed
v1:1.2.20.1210-2that now allows you to set custom launch flags in aspotify-flags.conffile under$XDG_CONFIG_HOMEor~/.config:)