makepkg
is currently failing for me, it looks like Spotify has started using a new key
==> Making package: spotify 1:1.2.26.1187-1 (Wed 24 Jan 2024 12:32:55 PM GMT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found spotify-1.2.26.1187-g36b715a1-x86_64.deb
-> Found spotify.sh
-> Found spotify.protocol
-> Found LICENSE
-> Found spotify-1.2.26.1187-1-Release
-> Found spotify-1.2.26.1187-1-Release.sig
-> Found spotify-1.2.26.1187-1-x86_64-Packages
==> Validating source files with sha512sums...
spotify-1.2.26.1187-g36b715a1-x86_64.deb ... Passed
spotify.sh ... Passed
spotify.protocol ... Passed
LICENSE ... Passed
spotify-1.2.26.1187-1-Release ... Skipped
spotify-1.2.26.1187-1-Release.sig ... Skipped
spotify-1.2.26.1187-1-x86_64-Packages ... Skipped
==> Verifying source file signatures with gpg...
spotify-1.2.26.1187-1-Release ... FAILED (unknown public key 6224F9941A8AA6D1)
==> ERROR: One or more PGP signatures could not be verified!
https://www.spotify.com/us/download/linux/ Suggests there's a new key to be used
https://download.spotify.com/debian/pubkey_6224F9941A8AA6D1.gpg
Pinned Comments
gromit commented on 2024-01-24 14:22 (UTC) (edited on 2024-12-28 11:34 (UTC) by gromit)
Please make sure to import the correct GPG 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, gpg 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-2
that now allows you to set custom launch flags in aspotify-flags.conf
file under$XDG_CONFIG_HOME
or~/.config
:)