| 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: | 172 |
| Popularity: | 10.46 |
| First Submitted: | 2023-02-09 22:51 (UTC) |
| Last Updated: | 2024-09-25 15:25 (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.
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.
@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.
@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.
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.
PKGBUILD failing for me as of 02∕13∕2024 with the following error:
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
@n0ob404 thanks for letting us know, I have updated the pkgbuild and pinned comment accordingly! :)
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.
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
Spotx works well with this
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:
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-2that now allows you to set custom launch flags in aspotify-flags.conffile under$XDG_CONFIG_HOMEor~/.config:)