Spotify client has a functionality to play local files that so far was broken in Gentoo because it required an old version of FFMpeg. For example, the current version so far was media-sound/spotify-1.1.42 which required libavcodec.so.54, provided by media-video/ffmpeg-3.4.6 which was removed from Portage one year before. For this reason, trying to play local files from Spotify client was throwing an error saying "Spotify can't play this right now". I was maintaining a custom version of the Spotify ebuild in my personal overlay which fetched the required old version of FFMpeg to compile it and bundle it with Spotify package fixing this issue: https://github.com/chusopr/chuso-overlay/blob/65e807c/media-sound/spotify/spotify-1.1.42.ebuild But Portage now includes version 1.1.55 of Spotify where it seems upstream finally caught up with modern versions of FFMpeg. The latest version of Spotify in Portage requires libavcodec.so.58 to fix local files playback, which is available in Portage. So maybe media-sound/spotify should now depend on media-video/ffmpeg:0/56.58.58 even if it's with an optional USE flag? It's not nice that the client throws such a generic error when we try to use one of its features, especially now that it can be fixed.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b5f4a04d54d0edfb6a96eb45b6d843c07905a0e0 commit b5f4a04d54d0edfb6a96eb45b6d843c07905a0e0 Author: Matthew Thode <prometheanfire@gentoo.org> AuthorDate: 2021-04-18 17:15:27 +0000 Commit: Matthew Thode <prometheanfire@gentoo.org> CommitDate: 2021-04-18 17:16:05 +0000 media-sound/spotify: add local-playback useflag Closes: https://bugs.gentoo.org/783501 Package-Manager: Portage-3.0.17, Repoman-3.0.2 Signed-off-by: Matthew Thode <prometheanfire@gentoo.org> media-sound/spotify/metadata.xml | 1 + media-sound/spotify/spotify-1.1.55.ebuild | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-)
