Package Details: spotify 1:1.2.42.290-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: Antiz
Votes: 165
Popularity: 7.03
First Submitted: 2023-02-09 22:51 (UTC)
Last Updated: 2024-07-22 14:00 (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 .. 8 9 10 11 12 13 14 Next › Last »

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.

ak42 commented on 2023-03-28 02:21 (UTC) 

spotify-1.1.84.716-13-x86_64-Packages: OK
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

fixed by switching back to stable, see:

http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages

versus

http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages

NicoHood commented on 2023-03-03 07:11 (UTC)

I've corrected the package now to build correct in a clean chroot.

Please make sure to import the correct GPG key first: curl -sS https://download.spotify.com/debian/pubkey_7A3A762FAFD4A51F.gpg | gpg --import -

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

pacman -S devtools base-devel
extra-x86_64-build

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.

mcgrew commented on 2023-02-23 12:10 (UTC) (edited on 2023-02-23 14:17 (UTC) by mcgrew)

Edit: This solution doesn't actually solve the problem, so never mind.

Big_Tea commented on 2023-02-14 09:15 (UTC)

Given that the key expired again recently, might be useful to re-add the comment about fixing the gpg key issue:

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

gj545rndmu commented on 2023-02-10 08:38 (UTC) (edited on 2023-02-10 09:12 (UTC) by gj545rndmu)

I hope the maintainer stops to change things so frequently... Just triggers too many unnecessary updates.

Maybe you should read the wiki: "As fixes and additional features are added to the PKGBUILD that influence the resulting package, the pkgrel should be incremented by 1."

It's about the resulting package, just pushing all that stuff that at the end was just about the installation process (anyways good that they were removed again...) and not influenced the resulting package was completely unnecessary. So we have to update ~10x to replace the package with the same files again?

eclairevoyant commented on 2023-02-10 08:18 (UTC)

@FoxBoron thanks for restoring this. My offer to maintain or comaintain still stands if you don't have time to update this package frequently, given your other extensive work as a TU.

gromit commented on 2023-02-10 01:36 (UTC)

@ToxicAven, the previous Maintainer deleted their account, this triggered a bug in AURWeb where the package was deleted with the maintainer (which is not supposed to happen). I discovered that, asked on IRC and the TUs restored the package.

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