Arch Linux User Repository

################################################################################
                 !!! IMPORTANT INSTRUCTIONS, READ CAREFULLY !!!
################################################################################
##
##  AUR/cider needs an Apple Music Token to work!
##
##  An Apple Music Token can be created via the Apple Developer Program.
##
##  https://developer.apple.com/documentation/applemusicapi/generating-developer-tokens
##
##  Once created, edit Cider's .desktop file
##
##    sudo nano /usr/share/applications/sh.cider.Cider.desktop
##  
##  Then in the Exec line add the TOKEN value.
##  For example, if your token is eyJhbGciOiJFUz, then Exec line will be:
##
##    Exec=env TOKEN=eyJhbGciOiJFUz CIDER_PORT=9000 /usr/bin/cider %U
##
##  Cider uses port 9000 by default. To change, edit CIDER_PORT variable.
##
##  Save the .desktop file and enjoy!
##
##
##  Important Links:
##
##   Installation Support: https://aur.archlinux.org/packages/cider
##  Current Upstream Fork: https://github.com/taoky/Cider
##     Abandoned Upstream: https://github.com/ciderapp/Cider
##
################################################################################

Package will not build using Paru. This is due to the file Cider/src/resources/version.sh needing to be chmoded after each time that git pull in the PKGBUILD is run. After making the file executable, it builds fine with makepkg but still not Paru.

Note: Have not tried other AUR helpers.

Hi, I don't think this can be built on armv7h.

It will download electron from https://github.com/castlabs/electron-releases/releases/tag/v21.0.0%2Bwvcus which doesn't provide any linux arm build.

package won't build on Node.js greater than 17. Use nodejs-lts-gallium instead of nodejs can build.

Thank you again for your great work.

Noted, thanks. I will move this to the stable branch, and create a bin package.

Thank you for maintain this package. But this package seems not building itself, and it's using 'deb' binary. I think it should be named 'cider-bin'

Ref: https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submission

I have been unable to recreate this issue. Usually the deb file would be downloaded into the src directory for the package.

Re-tested and failed with the same error. I noticed the "cider_1.5.399_amd64.deb" file downloads into my HOME directory. I'm not sure this is the correct place (espcially if you have something like firejail enabled).

❯ yay -S cider
:: There are 3 providers available for cider:
:: Repository AUR
    1) cider 2) cider-git 3) cider-minimal

Enter a number (default=1):
==> 1
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  cider-1.5.0-1

:: (1/1) Downloaded PKGBUILD: cider
  1 cider                            (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
:: (1/1) Parsing SRCINFO: cider
==> Making package: cider 1.5.0-1 (Sun 05 Jun 2022 07:01:50 PM)
==> Retrieving sources...
  -> Found cider.desktop
==> Validating source files with sha256sums...
    cider.desktop ... Passed
==> Making package: cider 1.5.0-1 (Sun 05 Jun 2022 07:01:52 PM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found cider.desktop
==> Validating source files with sha256sums...
    cider.desktop ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
==> Starting pkgver()...
==> Updated version: cider 1.5.399-1
==> Sources are ready.
==> Making package: cider 1.5.399-1 (Sun 05 Jun 2022 07:01:56 PM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Starting build()...
Building Cider on v1.5.399 : [Downloading Debian Package] | Extracting Package | Done
Building Cider on v1.5.399 : Downloading Debian Package | [Extracting Package] | Done
ar: *.deb: No such file or directory
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: cider

This might just be a bug with a GitHub release, retry the process and it should be fine.