Package Details: spotify 1:1.2.48.405-1

Git Clone URL: https://aur.archlinux.org/spotify.git (read-only, click to copy)
Package Base: spotify
Description: A proprietary music streaming service
Upstream URL: https://www.spotify.com
Licenses: custom
Submitter: Foxboron
Maintainer: gromit (Antiz)
Last Packager: gromit
Votes: 174
Popularity: 10.13
First Submitted: 2023-02-09 22:51 (UTC)
Last Updated: 2024-10-21 11:46 (UTC)

Pinned Comments

gromit commented on 2024-01-24 14:22 (UTC) (edited on 2024-02-22 23:00 (UTC) by gromit)

Please make sure to import the correct GPG key first:

$ curl -sS https://download.spotify.com/debian/pubkey_6224F9941A8AA6D1.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.

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 a spotify-flags.conf file under $XDG_CONFIG_HOME or ~/.config :)

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 Next › Last »

wunsz commented on 2023-04-21 09:19 (UTC) (edited on 2023-04-21 09:20 (UTC) by wunsz)

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

Wraaath commented on 2023-04-21 08:20 (UTC) (edited on 2023-04-21 11:46 (UTC) by Wraaath)

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.

Giulia commented on 2023-04-15 15:28 (UTC)

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?

ItachiSan commented on 2023-04-04 13:19 (UTC) (edited on 2023-04-04 13:20 (UTC) by ItachiSan)

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 -

sayang2001 commented on 2023-04-02 13:58 (UTC)

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

luisalcarasr commented on 2023-04-02 01:34 (UTC)

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.

adi222 commented on 2023-03-30 20:36 (UTC)

New version released: http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.2.8.923.g4f94bf0d_amd64.deb

teejer commented on 2023-03-29 22:49 (UTC) (edited on 2023-03-29 22:53 (UTC) by teejer)

I'm getting this error when trying to build.

I've removed the downloaded files and tried installing it again, but still get this error.

spotify-1.1.84.716-gc5f8b819-2-x86_64.deb: FAILED sha512sum: WARNING: 1 computed checksum did NOT match ==> ERROR: A failure occurred in prepare(). Aborting... -> error making: spotify-exit status 4 -> Failed to install the following packages. Manual intervention is required: spotify - exit status 4

Toku commented on 2023-03-29 01:33 (UTC) (edited on 2023-03-29 01:33 (UTC) by Toku)

For other people that have issues with the checksums, check them manually and remove the whole prepare section from the PKGBUILD and done.

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 Next › Last »