Package Details: spotify-tui 0.25.0-4

Git Clone URL: https://aur.archlinux.org/spotify-tui.git (read-only, click to copy)
Package Base: spotify-tui
Description: Spotify client for the terminal written in Rust
Upstream URL: https://github.com/Rigellute/spotify-tui
Keywords: spotify tui
Licenses: MIT
Submitter: flacks
Maintainer: orhun
Last Packager: orhun
Votes: 67
Popularity: 1.00
First Submitted: 2019-10-07 18:28 (UTC)
Last Updated: 2023-11-27 11:19 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

orhun commented on 2022-04-27 14:37 (UTC)

Updated the PKGBUILD with suggested patches.

The-Compiler commented on 2022-04-25 16:58 (UTC)

If you get an "unknown variant collection" error while trying to play liked songs, here is a workaround, including a patch to the PKGBUILD:

https://github.com/Rigellute/spotify-tui/issues/960#issuecomment-1108813658

Self-Perfection commented on 2021-11-05 03:07 (UTC)

spotify-tui has embedded completions for shells (bash /zsh / ...). I've made a patch for PKGBUILD that adds installation of these completions: https://gist.github.com/97331cff9cace2fe8de674a77d1e46b3

apropos commented on 2021-05-21 21:34 (UTC)

@bryan.abrams and @andrea.denisse: spotify-tui's binary name is spt

bryan.abrams commented on 2021-05-03 22:47 (UTC)

I'm having the same issue as @andrea.denisse

The package is installed but there's no binary in /usr/bin

denisse commented on 2021-04-26 06:05 (UTC)

Hello, the package builds and appears to install but I'm unable to find it. I think this happens because the PKGBUILD is missing the following lines:

provides=('spotify-tui')
conflicts=('spotify-tui')

sam-kirby commented on 2020-07-20 18:44 (UTC)

@Conni2461 that does indeed fix the issue, thank you!

Conni2461 commented on 2020-07-20 17:30 (UTC) (edited on 2020-07-20 17:35 (UTC) by Conni2461)

@sam-kirby thanks for reporting that issue.

I will continue to use cargo build rather than cargo install because the package stage is responsible for copying files to $pkgdir/usr. I fixed it with the --target-dir option. I also tested it with env var CARGO_TARGET_DIR and it worked. I hope this fixes your issue.

sam-kirby commented on 2020-07-20 14:07 (UTC)

This fails to create the package with the following error if CARGO_TARGET_DIR is set.

==> Starting package()...
install: cannot stat 'target/release/spt': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...
error making: %!s(func() string=0x55a92f70ca60)

Instead of using install with fixed path, instead you could consider using cargo install --root "$pkgdir/usr" --path "$srcdir/$pkgname-$pkgver".

Conni2461 commented on 2020-05-27 21:29 (UTC) (edited on 2020-05-27 21:29 (UTC) by Conni2461)

I was not able to reproduce the error inside a docker container.

The cargo directory should be in the home directory. You can set the directory using the env variable CARGO_HOME. So make sure that the env variable is not set anywhere in your profile or set it to export CARGO_HOME="$HOME"/.cargo or better export CARGO_HOME="$XDG_DATA_HOME"/cargo if you use xdg.

Also make sure that you clone the aur repository again before running makepkg.

« First ‹ Previous 1 2 3 Next › Last »