Package Details: spicetify-cli 2.5.0-1

Git Clone URL: (read-only, click to copy)
Package Base: spicetify-cli
Description: Command-line tool to customize Spotify client
Upstream URL:
Keywords: customization spotify theme
Licenses: GPL
Submitter: khanhas
Maintainer: khanhas
Last Packager: khanhas
Votes: 28
Popularity: 2.96
First Submitted: 2019-01-11 04:14
Last Updated: 2021-06-27 16:18

Latest Comments

1 2 Next › Last »

clydedroid commented on 2021-09-03 19:16

Looks like spotify has finally been updated to 1:, so the latest version of spicetify finally works!

WaterInMyLungs commented on 2021-08-11 23:11

This version does work with the spotify 1: on the AUR I am currently running Dribbblish theme. Make sure to run the commands on I was having issues trying to get it to work when I was only running spicetify config current_theme Dribbblish color_scheme base

KooshaPari commented on 2021-06-07 16:53

Is there any reason why this package is above 1.2.1? All versions of spicetify past that do not support the latest version of spotify that is built for linux, which means until spotify releases 1.1.58 or greater, we can't use any version of spicetify past 1.2.1

BachoSeven commented on 2021-05-15 13:28

sha256sums for the tarball are outdated:

==> Validating source files with sha256sums...
    v2.1.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

rien333 commented on 2021-02-03 08:25

EDIT: nvm, fixed by clearing yay's cache of spicetify.

Pleause update the shasum:

==> Making package: spicetify-cli 1.2.0-1 (Wed 03 Feb 2021 09:23:54 AM CET)
==> Retrieving sources...
  -> Downloading v1.2.0.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   129    0   129    0     0    486      0 --:--:-- --:--:-- --:--:--   486
100  616k  100  616k    0     0   864k      0 --:--:-- --:--:-- --:--:--  864k
==> Validating source files with sha256sums...
    v1.2.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

rility commented on 2020-04-24 16:25

It would be best if you can add:

post_install() {
  cat << EOF
  ===> spicetify-cli post install message:
  ===> Before applying Spicetify, you need to gain write permission on Spotify 
files, by running command:
  ===> $ sudo chmod 777 /opt/spotify -R

masterkorp commented on 2019-08-26 15:19

Hello, I am unable to build.

-> % makepkg ==> Making package: spicetify-cli 0.9.3-1 (seg 26 ago 2019 16:15:03 WEST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found v0.9.3.tar.gz ==> Validating source files with sha256sums... v0.9.3.tar.gz ... Passed ==> Extracting sources... -> Extracting v0.9.3.tar.gz with bsdtar ==> Removing existing $pkgdir/ directory... ==> Starting build()...


/usr/lib/go/src/bytes/bytes_decl.go:10:6: IndexByte redeclared in this block previous declaration at /usr/lib/go/src/bytes/bytes.go:101:34 /usr/lib/go/src/bytes/bytes_decl.go:17:6: Equal redeclared in this block previous declaration at /usr/lib/go/src/bytes/bytes.go:18:25 /usr/lib/go/src/bytes/bytes_decl.go:24:6: Compare redeclared in this block previous declaration at /usr/lib/go/src/bytes/bytes.go:37:27


/usr/lib/go/src/strings/strings_decl.go:8:6: IndexByte redeclared in this block previous declaration at /usr/lib/go/src/strings/strings.go:150:34 ==> ERROR: A failure occurred in build(). Aborting...

khanhas commented on 2019-07-14 17:17

@ModeImat: Thank you. It is fixed.

@riend333: You're right. I used go-pie since I didn't know how to make AUR package before and I just used other Go depended packages' PKGBUILD out there as reference and they all use go-pie. Anyway, it is changed. Thank you very much.

Modelmat commented on 2019-07-14 10:58

This package creates a "go" folder in $HOME. I believe the following code is responsible, as it gets created when building.

build() {
  cd "$pkgname-$pkgver"
  go build -o spicetify

This is rather irritating. Please fix it.

rien333 commented on 2019-06-17 19:50

Any reason for the go-pie dependency? From what I understand, go-pie's benefits are mostly security related, and I don't see how security factors in a spotify-themer that mostly just changes a bunch of css/javascript around. I see that go-pie "provides" go (as a sort of meta-package), so maybe you could just check the precense for this meta-package for the people that insist on using go-pie? (kinda nice for people like me that already have go, but don't see a need to have yet another version). Furthermore, it builds perfectly fine with the normal go.