Arch Linux User Repository

Please make sure to import the correct GPG key first:

$ curl -sS https://download.spotify.com/debian/pubkey_C85668DF69375001.gpg | gpg --import -

And always build in a clean chroot. It is as easy as:

pacman -S devtools
git clone https://aur.archlinux.org/spotify.git
cd spotify
pkgctl build
pacman -U <path-to-spotify-package>

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.

@lightofpast Just pushed v1:1.2.20.1210-2 that now allows you to set custom launch flags in a spotify-flags.conf file under $XDG_CONFIG_HOME or ~/.config :)

I'm getting A failure occurred in prepare when I try to build. I also tried running extra-x86_64-build, but got the same error.

[spotify]$ gpg --list-keys
~/.gnupg/pubring.kbx
------------------------------
pub   rsa4096 2022-11-14 [SC] [expires: 2024-02-07]
      E27409F51D1B66337F2D2F417A3A762FAFD4A51F
uid           [ unknown] Spotify Public Repository Signing Key <tux@spotify.com>

[spotify]$ git log -1
commit 070a1ca64433822f74b02bb88b82a223f05c48ab (HEAD -> master, origin/master, origin/HEAD)
Author: NicoHood <git@nicohood.de>
Date:   Wed Apr 5 09:21:36 2023 +0200

    1.2.8.923

[spotify]$ makepkg -sirc
==> Making package: spotify 1:1.2.8.923-1 (Fri 21 Apr 2023 11:59:41 AM PDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found spotify.protocol
  -> Found LICENSE
  -> Downloading spotify-1.2.8.923-g4f94bf0d-x86_64.deb...
  -> Downloading spotify-1.2.8.923-1-Release...
  -> Downloading spotify-1.2.8.923-1-Release.sig...
  -> Downloading spotify-1.2.8.923-1-x86_64-Packages...
==> Validating source files with sha512sums...
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.2.8.923-g4f94bf0d-x86_64.deb ... Passed
    spotify-1.2.8.923-1-Release ... Skipped
    spotify-1.2.8.923-1-Release.sig ... Skipped
    spotify-1.2.8.923-1-x86_64-Packages ... Skipped
==> Verifying source file signatures with gpg...
    spotify-1.2.8.923-1-Release ... Passed
==> Extracting sources...
  -> Extracting spotify-1.2.8.923-g4f94bf0d-x86_64.deb with bsdtar
==> Starting prepare()...
spotify-1.2.8.923-1-x86_64-Packages: OK
spotify-1.2.8.923-g4f94bf0d-x86_64.deb: FAILED
sha512sum: WARNING: 1 computed checksum did NOT match
==> ERROR: A failure occurred in prepare().
    Aborting...

I managed to install heading to .cache/yay/spotify, and running:

makepkg --syncdeps --noprepare --install

hint: I used to skip package() with --noprepare

as I had error ==> ERROR: A failure occurred in package(). Aborting...

it works, and installs, all I could care

@wunsz
You are using the --noextract while installing. This prevents the program from actually extracting source files that are needed for the installation. I updated my comment so you can see what I did.

Hey! I'm still having problems installing Spotify using version 1.2.8.923-1:

❯ yay -Sy --mflags --noextract spotify

==> Making package: spotify 1:1.2.8.923-1 (pią, 21 kwi 2023, 11:14:30)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Sources are ready.
==> Making package: spotify 1:1.2.8.923-1 (pią, 21 kwi 2023, 11:14:31)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Entering fakeroot environment...
==> Starting package()...
tar (child): data.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
==> ERROR: A failure occurred in package().
    Aborting...
 -> error making: spotify-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
spotify - exit status 4

Since the checksums seem to always be outdated I just installed Spotify ignoring the checksums. Keep in mind, this is not an actual fix, this just ignores the problem.
First I did a regular install with yay -S spotify.
In .cache/yay/spotify I ran makepkg --noextract --syncdeps --install.
Hope this helps.

After importing the new gpg public key (pubkey_7A3A762FAFD4A51F.gpg), spotify-1.2.8.923-1-Release's gpg signature fails to be verified. In my keyring the gpg key is shown as uid [unknown] Spotify Public Repository Signing Key <tux@spotify.com>. Am i missing something?

Patch for the current PKGBUILD, if you want to build the package ASAP:

diff --git a/PKGBUILD b/PKGBUILD
index 806444e..15ec203 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -5,10 +5,10 @@
 # Contributor: Eothred <yngve.levinsen@gmail.com>

 pkgname=spotify
-pkgver=1.1.84.716
+pkgver=1.2.8.923
 epoch=1
-_commit=gc5f8b819-2
-pkgrel=13
+_commit=g4f94bf0d
+pkgrel=1
 pkgdesc='A proprietary music streaming service'
 arch=('x86_64')
 license=('custom')
@@ -34,10 +34,10 @@ source=('spotify.protocol'
         "${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages")
 sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
-            '9ba6c2d155f683b9a38222d58a2a53a2a5f4b422ed1c0d603af87919ba8a68309aea3354278fd1d5d8142a1568d93b7e83b14c041e749b0c39f3bc155a633ef8'
+            'd4bc076d87018c851f851cc8b65e05b1611701994a97963bd63aa816518b1f5fa4d89956fea8ef234a41f1c4d6f8a3aa2bfc4fbd3b39f58f0bed5aec79c60edc'
+            '21d4404a037b4d7b6e8dcc8e98f2a9d4742d5775e3e6b0cf813f95f79fb3aee5e4395795d39dccbfe264bf74b340c3d18870f19967db8889fdd7b3e7715bb9bb'
             'SKIP'
-            'SKIP'
-            'SKIP')
+            'fd3fbf7207bc323a85ccf95709b7becd231931939414df55a67942b449ac9cd8ecdf41b3a4885209ea336fbfaed0e3d8244a7263e85f4c9e6da0d5da03618626')

 # Import key with:
 # curl -sS https://download.spotify.com/debian/pubkey_7A3A762FAFD4A51F.gpg | gpg --import -

can the maintainer update the checksum? it has been more than a week now.

If you want to skip the checksums, add the --noextract flag to makepkg, for example: yay -Syu --mflags --noextract spotify. This is not a recommendation, do it at your own risk, checksums have their reason for existing.