Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[email protected]: Shim creation fail #12051

Closed
4x0v7 opened this issue Oct 17, 2023 · 1 comment · Fixed by #12163
Closed

[email protected]: Shim creation fail #12051

4x0v7 opened this issue Oct 17, 2023 · 1 comment · Fixed by #12163

Comments

@4x0v7
Copy link

4x0v7 commented Oct 17, 2023

Cannot shim 'reamote.exe': File does not exist

 PS> scoop install reaper
Installing 'reaper' (7.001) [64bit] [extras]
WARN  By installing you accept following license: Proprietary (https://www.reaper.fm/dist-agreement.php)
reaper7001_x64-install.exe (14.9 MB) [============================================================================================================] 100%
Checking hash of reaper7001_x64-install.exe ... ok.
Extracting dl.7z ... done.
Running installer script...
Linking ~\scoop\apps\reaper\current => ~\scoop\apps\reaper\7.001
Creating shim for 'reaper'.
Creating shim for 'reamote'.
ERROR Cannot shim 'reamote.exe': File does not exist
@pomberger
Copy link
Contributor

I got the same error and fixed it by manually removing the shim creation for reamote in the manifest.

The reamote.exe is missing in the reaper 7.001 installation. This is why the shim creation fails.
I couldn't find out, if this is intended in the new release of reaper. However, if you download and run the installer manually from reaper.fm you see, there is no more option to install reamote, as it was in the installer of reaper 6.x.

Seems to be the same in the macOS installation:
https://forum.cockos.com/showpost.php?p=2722121&postcount=135

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants