zelikos / davincibox

Container for DaVinci Resolve installation and runtime dependencies on Linux
Apache License 2.0
224 stars 10 forks source link

New setup.sh file is unable to use .run installer #91

Closed ItsRogueRen closed 5 months ago

ItsRogueRen commented 5 months ago

Cannot extract the .run file on latest setup.sh file in Releases (as of 06-20-2024). Error states that it cannot determine if the .run is a valid installer for Resolve despite the same file working for previous releases.

Installation method used

To Reproduce

Steps to reproduce the behavior:

  1. Go to Releases
  2. Download the latest version 1.2.0
  3. Follow the instructions for running setup.sh
  4. See error

Expected behavior

.run file to be extracted and install Resolve within a Davincibox

System information (please complete the following)

Additional context Can be worked around by using 1.1.0 and then upgrading.

zelikos commented 5 months ago

Latest setup.sh did successfully extract the .run installer for me (though I have a separate, non-breaking error I need to troubleshoot now...)

Copy-paste the full terminal output from your attempt

ItsRogueRen commented 5 months ago

Latest setup.sh did successfully extract the .run installer for me (though I have a separate, non-breaking error I need to troubleshoot now...)

Copy-paste the full terminal output from your attempt

I just shut down my PC for the night, I'll edit this in the morning with the output

ItsRogueRen commented 5 months ago

Latest setup.sh did successfully extract the .run installer for me (though I have a separate, non-breaking error I need to troubleshoot now...)

Copy-paste the full terminal output from your attempt

Here is the error after running

Extracting DaVinci_Resolve_18.6.5_Linux.run ... ./setup.sh: line 52: DaVinci_Resolve_18.6.5_Linux.run: command not found DaVinci_Resolve_18.6.5_Linux.run could not be extracted. Please double-check that it is a valid DaVinci Resolve installer.

zelikos commented 5 months ago

Looks like the issue was an oversight from #88. Should be fixed now in 1.3.0

If the issue persists with the updated script, please reopen this issue.