Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - spotify-legacy

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: spotify-legacy 0.9.17-2

Git Clone URL: https://aur-dev.archlinux.org/spotify-legacy.git (read-only)
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=0.9.17
Submitter: olejon
Maintainer: None
Last Packager: Scimmia
Votes: 29
Popularity: 1.191458
First Submitted: 2016-04-30 17:14
Last Updated: 2016-08-25 15:37

Pinned Comments

Scimmia commented on 2016-08-25 15:38

You will need to uninstall 0.9.17-1 before updating to 0.9.17-2. Sorry, the old package put untracked files all over the place, nothing else we can do.

If you still get conflicting file errors, please see https://wiki.archlinux.org/index.php/Pacman#.22Failed_to_commit_transaction_.28conflicting_files.29.22_error
It's very possible even uninstalling doesn't completely clean up the mess.

Latest Comments

1 2 Next › Last »

Scimmia commented on 2016-08-25 15:38

You will need to uninstall 0.9.17-1 before updating to 0.9.17-2. Sorry, the old package put untracked files all over the place, nothing else we can do.

If you still get conflicting file errors, please see https://wiki.archlinux.org/index.php/Pacman#.22Failed_to_commit_transaction_.28conflicting_files.29.22_error
It's very possible even uninstalling doesn't completely clean up the mess.

Scimmia commented on 2016-08-22 15:03

Ping? You've created quite a mess here.

Scimmia commented on 2016-08-20 06:59

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

olejon commented on 2016-04-30 17:28

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

mis commented on 2016-04-09 13:44

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

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

mis commented on 2016-04-09 09:39

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

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

Done

Freso commented on 2016-02-22 09:56

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