Package Details: reaper-bin 6.13-1

Git Clone URL: https://aur.archlinux.org/reaper-bin.git (read-only, click to copy)
Package Base: reaper-bin
Description: Digital Audio Workstation
Upstream URL: http://www.reaper.fm
Licenses: custom
Conflicts: reaper
Submitter: david0
Maintainer: david0
Last Packager: david0
Votes: 75
Popularity: 1.56
First Submitted: 2018-08-10 15:40
Last Updated: 2020-07-23 13:30

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

capoeira commented on 2018-08-01 10:23

@cogwerkz that's not the case here. I installed excluding those two ln lines

cogwerkz commented on 2018-08-01 10:18

@capoeira it works fine from the terminal. You just have to type reaper5, not reaper. :)

capoeira commented on 2018-08-01 10:11

actualy the binary should go to /usr/bin/, no? that's why you can't even run it with a simple "reaper" from terminal

pha-qu commented on 2018-08-01 00:33

Anyone scratching there heads, after you get 'ln: failed to create symbolic link' error pull up a terminal, and: cd /tmp/pamac-build-yourusername (or where ever pamac does the magic) sudo nano PKGBUILD CTRK-w (then type 'ln' and hit enter) add '#' symbol to the start of the two lines that start ln CTRL-o CTRL-x makepkg -c sudo pacman -U reaper-5.94rc1-1-x86_64.pkg.tar.xz Y<agree> sudo nano /usr/share/applications/cockos-reaper.desktop (or wherever your desktop config is stored) remove the 5 from this line: Exec=/usr/lib/REAPER/reaper5 %F to: Exec=/usr/lib/REAPER/reaper %F CTRL-o CTRL-x</agree>

Now test your menu entry item, and reaper should be good to go ;)

pha-qu commented on 2018-08-01 00:19

@david0 can you please desist from pushing broken updates that don't have a hope in Hades of updating. The PKGBUILD is still not working: ln: failed to create symbolic link '/tmp/pamac-build-pha-qu/reaper/pkg/reaper/usr/bin/reaper': File exists ==> ERROR: A failure occurred in package(). Experimental or not, the install script

echo "PLEASE NOTE -- REAPER for Linux is an unsupported experimental version." is not an excuse for not testing an update before pushing it out.

The install.sh script, I repeat, appears or is creating the required symlinks automagically. Removing lines ln ... from PKGBUILD results in a successful update

... end of transmission

capoeira commented on 2018-07-31 16:53

I see. I misunderstood his message. thought he was the owner. NOW: the version just changed to RC. I will mark the package

funkmuscle commented on 2018-07-31 15:52

hey @cap, pha-qu method worked

capoeira commented on 2018-07-31 13:33

I get the same error as Funk

pha-qu commented on 2018-07-30 20:02

Current pkgbuild fails. ln: failed to create symbolic link '/tmp/pamac-build-spongebob/reaper/pkg/reaper/usr/bin/reaper': File exists

I think those two ln's in the PKGBUILD are causing this, I think the reaper install script is already creating those symlinks quietly.

I've removed those lines from the PKGBUILD, done an offline build, and am back in business

PS .desktop entry for me still (WTF) points to 'reaper5' executable in lib folder, so you may need to change that to 'reaper', an upstream issue.

funkmuscle commented on 2018-07-30 17:51

build fails:

PLEASE NOTE -- REAPER for Linux is an unsupported experimental version.


REAPER installer -- install to /tmp/trizen-harv/reaper/pkg/reaper/usr/lib

Copying files... done Writing uninstall script to /tmp/trizen-harv/reaper/pkg/reaper/usr/lib/REAPER/uninstall-reaper.sh

*** Installation complete ln: failed to create symbolic link '/tmp/trizen-harv/reaper/pkg/reaper/usr/bin/reaper': File exists ==> ERROR: A failure occurred in package(). Aborting... :: Unable to build reaper - makepkg exited with code: 4