Package Details: spotify-legacy 0.9.17-3

Git Clone URL: https://aur.archlinux.org/spotify-legacy.git (read-only, click to copy)
Package Base: spotify-legacy
Description: A proprietary music streaming service.
Upstream URL: https://www.spotify.com/download/linux/
Licenses: custom
Conflicts: spotify, spotify-beta, spotify-stable, spotify094
Provides: spotify
Submitter: olejon
Maintainer: olejon
Last Packager: olejon
Votes: 34
Popularity: 0.000002
First Submitted: 2016-04-30 17:14 (UTC)
Last Updated: 2017-06-09 10:36 (UTC)

Pinned Comments

olejon commented on 2019-03-09 17:37 (UTC) (edited on 2019-03-09 18:44 (UTC) by olejon)

It is a problem with the ffmpeg0.10 package. The solution is posted below and in that package's comments, and x264 (video decoding) is not needed for local files playback - you have the regular ffmpeg package alongside this installed for that - so no problem not compiling it in.

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

Scimmia commented on 2016-08-22 15:03 (UTC)

Ping? You've created quite a mess here.

Scimmia commented on 2016-08-20 06:59 (UTC)

This doesn't actually create a package? It really, really needs fixed.

olejon commented on 2016-04-30 17:28 (UTC)

I have uploaded a new package called spotify-legacy, and asked for a merge.

<deleted-account> commented on 2016-04-09 13:44 (UTC)

Renaming this to spotify-legacy would match my suggestion. ;) If the difference between the testing and stable 1.0 versions is not really big, I agree with you that there is no need for a package spotify-stable, since there are already spotify and spotify-beta providing the testing version.

olejon commented on 2016-04-09 13:16 (UTC)

It is correct that Spotify has promoted v 1.0 as stable, but it really isn't (see links below), but I see your point regarding the name. I don't see much point in making a package for the stable version of v 1.0 as it is not really stable compared to the testing version. The testing version is the one kept in sync with the Windows and Mac versions. Also this package here because of SpotCommander, since v 1.0 is buggy and broken in several ways (in this case the broken MPRIS support is the reason). I like more the idea of renaming it to spotify-legacy or maybe spotify-qt, as up until v 1.0 Spotify for Linux was QT-based with some GTK-elements as well, while v 1.0 is just a web app in CEF (Chromium Embedded Frame). https://community.spotify.com/t5/Help-Desktop-Linux-Windows-Web/Linux-Spotify-client-1-x-now-in-stable/m-p/1300404/highlight/true#M151493 https://community.spotify.com/t5/Help-Desktop-Linux-Windows-Web/Linux-Spotify-DBus-MPRIS2-support-not-fully-working/m-p/1208249/highlight/true#M139899

<deleted-account> commented on 2016-04-09 09:39 (UTC)

Update this package to the latest stable version, which is currently 1.0.25.127, and maybe create a new package spotify-legacy for version 0.9.17 makes more sense to me.

Louis commented on 2016-04-08 23:39 (UTC)

Spotify has now marked their 1.x builds as stable for Linux. Shouldn't this package be renamed to spotify-lagacy?

olejon commented on 2016-03-10 18:00 (UTC)

Done

Freso commented on 2016-02-22 09:56 (UTC)

Perhaps add "spotify" to $provides in addition to $conflicts?

olejon commented on 2016-02-08 09:39 (UTC)

Done. You must be running a very lightweight installation. I am building on a ArchBang VM which is very lightweight, but has gconf apparently.

« First ‹ Previous 1 2 3 Next › Last »