| 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: | 151 |
| Popularity: | 13.80 |
| First Submitted: | 2023-02-09 22:51 (UTC) |
| Last Updated: | 2024-02-21 23:20 (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.
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
@bosma @me44ic05 Was getting the same error with download failing midway. Out of desperation I re-imported the GPG key despite already having it "curl -sS https://download.spotify.com/debian/pubkey_7A3A762FAFD4A51F.gpg | gpg --import -a" and it started working again. Might help.
I'm not sure what went on with the latest changes for the Spotify client or GNOME, but, if you leave the "minimize on close" option on, lock your screen, and unlock it back, Spotify breaks the interactions with the windows (close, select tab etc). I'm trying to understand the extent of the error before I file a more detailed bug report.
@bosma I've been getting the same. The main package download will fail with some arbitrary number of bytes remaining. I've had to clone this repo and manually run makepkg -i multiple times every time there's an update to get it to push through to a fully complete download.
I think it may be isolated to some networks: jumping on a VM on a cloud provider seemed to present no issue with downloading the package. I haven't looked much further though.
@sterni1971 A new version came out in the meantime (v1.2.25.1011) causing the upgrade to v1.2.25.1009 to fail. I just updated the package ;)
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:)