Package Details: spotify 1:1.2.60.564-2

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: 206
Popularity: 8.46
First Submitted: 2023-02-09 22:51 (UTC)
Last Updated: 2025-04-07 11:54 (UTC)

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:

$ 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.

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 .. 3 4 5 6 7 8 9 10 11 12 13 .. 19 Next › Last »

Antiz commented on 2024-02-23 07:34 (UTC) (edited on 2024-02-23 07:36 (UTC) by Antiz)

@kminardo Not really unfortunately... As said in the pinned comment, spotify continuously changes download binaries, GPG keys, etc... which is not appropriate, but we cannot do anything about it at our level.

The correct GPG key to import is noted/updated in the "Debian / Ubuntu" install instructions of this link. So if you get an error related to GPG key, you can check this link to see if it changed and adapt the command in the pinned comment with the new key (and also notify us so we can adapt the instructions in the pinned comment and in the PKGBUILD).

I guess one could set urlwatch (or something) to monitor this webpage to get notified of changes, but all can we do at our level on that matter is to relay Spotify's instructions. So I guess your best chance to keep up with the GPG key changes is to regularly check the "Debian / Ubuntu" install instructions of this link to see if the key has been replaced by a new one (and to notify us if it's the case so we can adapt the instructions there)! :D

kminardo commented on 2024-02-23 02:36 (UTC)

Is there any recommended approach to keep up with the GPG key changes? Right now, I only know to check these comments to see if anyone reported a build failure, and hope gromit replied with a url

kjkent commented on 2024-02-23 00:13 (UTC)

@gromit must be a slow brain day as I should have run paru -Scc instead. I also didn't realise AUR helpers were unsupported! How on earth do you manage tracking and building updates manually? nvchecker + scripts?

I appreciate the help regardless, clean cache & a chroot build seems to have done the job.

gromit commented on 2024-02-22 22:58 (UTC)

so I cleared all caches with pacman -Scc - same result.

This is only clearing pacman related caches and not whatever your AUR helper does (refer to its documentation on how to clear caches.

AUR Helpers are not supported anyways, please build and install with the methods described in the Wiki or in the pinned comment.

If this impacts others I'll post whatever fix I find

I like your spirit, but this is a problem very much specific to your setup!

@VetheonGames' paste no longer exists so I'm unsure if related.

They had some (network related) download issues if I remember correctly.

kjkent commented on 2024-02-22 22:45 (UTC) (edited on 2024-02-22 22:46 (UTC) by kjkent)

@gromit thanks for the reply. Installing via paru -Syu spotify. I thought the same thing, so I cleared all caches with pacman -Scc - same result.

Can confirm this error is confined to my machine (8th gen i5 laptop), as I've just successfully installed on another (Ryzen 3600X desktop). Removing the package also works totally fine, so no out-of-transaction file changes. Same install process on two machines running the same arch with a near identical setup. ¯\_(ツ)_/¯ If this impacts others I'll post whatever fix I find. @VetheonGames' paste no longer exists so I'm unsure if related.

Sorry for the noise.

gromit commented on 2024-02-22 22:14 (UTC)

@kjkent, how are you trying to install this package? It sounds like you had some issue with the built package, but that has most likely nothing to do with an error in the PKGBUILD.

kjkent commented on 2024-02-22 21:45 (UTC)

1:1.2.31.1205-2 fails at the install step with:

error: could not extract /opt/spotify/libcef.so (Truncated zstd input)
error: problem occurred while installing spotify
error: could not commit transaction
error: failed to commit transaction (transaction aborted)

Also seems files are installed outside of $pkgdir as files are placed in /opt/spotify despite the aborted transaction.

VetheonGames commented on 2024-02-13 20:37 (UTC) (edited on 2024-02-13 20:40 (UTC) by VetheonGames)

PKGBUILD failing for me as of 02∕13∕2024 with the following error:

https://snippet.host/hdsdcf

Attempted manual build in clean chroot, and dirty build with yay not in a clean chroot. Even reimported the gpg key, still same issue.

EDIT:

Just tried the build over and over and over, eventually it seemed to successfully download things and build them. Don't know what happened, please disregard my earlier comment

gromit commented on 2024-01-24 14:23 (UTC)

@n0ob404 thanks for letting us know, I have updated the pkgbuild and pinned comment accordingly! :)

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 19 Next › Last »