Permission denied with 2.7.0
See original GitHub issueWhen installing kscript
via:
sdk install kscript
Things worked great for version 2.6.0
, whereas I had a Kotlin script that began with the following header:
#!/usr/bin/env kscript
Unfortunately something seems to have changed, as now with 2.7.0
I’m getting the following error when I try to run Kotlin scripts:
/usr/bin/env: 'kscript': Permission denied
(this was seen on a CI system so it is from a fresh install of kscript
, not an upgrade)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7
Top Results From Across the Web
"Permission denied" issue still happening with gh 2.7.0 #738
Version number 2.7.0 Describe the bug I installed gh globally and when I try to send a pull request, it fails to open...
Read more >Ruby Version Failure 2.7.0: Error: Permission denied ...
This is unrelated to rvm itself. To install required dependencies for your ruby, rvm used your installed homebrew.
Read more >Backup fails with "Permission denied" error - GitLab.org
Hello, I'm desperately getting this error while trying to backup my gitlab setup. It's a from source installation.
Read more >[Solved]-Ruby Version Failure 2.7.0: Error: Permission denied ...
This is unrelated to rvm itself. To install required dependencies for your ruby, rvm used your installed homebrew. However, during cleanup of your...
Read more >Container permission denied: How to diagnose this error
Learn what is causing a container permissions error and how to work around the issue without resorting to the --privileged flag.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Indeed. There seems to be an issue with the sdk installation. I’ll update it shortly. Meanwhile you could use sdkman to rollback to the old release.
I’m on holidays atm but I’ll remove 2.7.0 from sdkman when I get to a computer. Alternatively, someone can simply raise a PR on our DB migrations repo.