Package Details: spotify-dev 1.2.31.1205-1

Git Clone URL: https://aur.archlinux.org/spotify-dev.git (read-only, click to copy)
Package Base: spotify-dev
Description: A proprietary music streaming service
Upstream URL: https://www.spotify.com
Licenses: custom
Conflicts: spotify
Provides: spotify
Submitter: imp0
Maintainer: imp0 (midnightfox, sorcix)
Last Packager: imp0
Votes: 25
Popularity: 0.000250
First Submitted: 2019-02-19 21:06 (UTC)
Last Updated: 2024-02-29 18:00 (UTC)

Required by (19)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

ElijahLynn commented on 2020-09-29 00:35 (UTC)

GPG key import failure:

:: PGP keys need importing: -> 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90, required by: spotify-dev ==> Import? [Y/n] :: Importing keys with gpg... gpg: keyserver receive failed: General error problem importing keys

gunslingerfry commented on 2020-09-23 17:07 (UTC) (edited on 2020-09-23 17:12 (UTC) by gunslingerfry)

There's something weird about the repository.spotify.com server. There are frequent failures to download. The PKGBUILD probably needs to make multiple attempts before failing. wget always gets booted near the end of the download and has to retry.

snek commented on 2020-09-22 19:19 (UTC) (edited on 2020-09-22 19:27 (UTC) by snek)

Installing ffmpeg0.10 as the package suggests does not fix the "Spotify can't play this right now" message when trying to play a local file.

bulletmark commented on 2020-09-18 21:53 (UTC)

@Tobleh, if I say I changed the https to http and there is only one https in the file then pretty clearly that is the line I changed! I tried many times using https yesterday and it failed. Then I changed it to http and it worked and I tested that 2 times to confirm. However, after your comment, I tested again today and it is not working with either https or http.

Tobleh commented on 2020-09-18 18:44 (UTC) (edited on 2020-09-18 22:13 (UTC) by Tobleh)

@bulletmark

The url is already http, and yet I still have a download fail when I use makepkg -si. Speaking of that, when I perform that command, I get this.

==> Making package: spotify-dev 1.1.42.622-1 (Fri 18 Sep 2020 02:38:50 PM) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading spotify-Release... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2447 100 2447 0 0 5024 0 --:--:-- --:--:-- --:--:-- 5024 -> Found spotify-Release -> Downloading spotify-1.1.42.622-x86_64.deb... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 1 120M 1 2076k 0 0 403k 0 0:05:05 0:00:05 0:05:00 484k curl: (18) transfer closed with 124167036 bytes remaining to read ==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb Aborting...

That URL is already http, unless you mean changing the URL in line 15 of the PKGBUILD from https to http - in which case the download still fails with a similar error.

EDIT: welp it works again when I tried again and forgot to do a clean build or change the PKGBUILD back to https from http

so idk what the fuck happened with me

bulletmark commented on 2020-09-17 23:09 (UTC) (edited on 2020-09-17 23:10 (UTC) by bulletmark)

The download fails part way for me when yay tries updating this to 1.1.42.622-1 today. Changing the url from https to http makes it succeed.

baizon commented on 2019-07-20 09:53 (UTC) (edited on 2019-07-20 09:57 (UTC) by baizon) 

spotify-x86_64-Packages: OK
spotify-1.1.5.153-x86_64.deb: FAILED
sha512sum: WARNING: 1 computed checksum did NOT match
==> ERROR: A failure occurred in prepare().

Pacaur caches by default. Removing ~/.cache/pacaur solved the problem for me.

mokkurkalve commented on 2019-07-19 13:01 (UTC)

Building ffmpeg0.10 now fails, also building in clean chroot the recommended way.

Plexcon commented on 2019-05-01 23:29 (UTC) (edited on 2019-05-01 23:30 (UTC) by Plexcon)

Ok with Trizen

imp0 commented on 2019-05-01 20:51 (UTC)

This is probably because you're building from a location that hast leftovers from a previous build.

I'd recommend to always build your packages starting from a clean source and in a clean environment. This should save you from most troubles.

« First ‹ Previous 1 2 3 4 5 Next › Last »