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

Curl-fetched entrypoint (arturo.sh) not automatically executable #1279

Open
Ryton opened this issue Oct 5, 2023 · 4 comments
Open

Curl-fetched entrypoint (arturo.sh) not automatically executable #1279

Ryton opened this issue Oct 5, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@Ryton
Copy link

Ryton commented Oct 5, 2023

Describe the bug
When pulling and installing a nightly or stable arturo version through curl on linux, it is placed correctly in /home//.arturo/bin/
but it is not executable by default (chmod !=666)

This causes an error "arturo not found" when running $ arturo

To Reproduce
Steps to reproduce the behavior:

  1. download nightly or stable "curl -sSL https://get.arturo-lang.io/latest | sh"
  2. run arturo
  3. See error

Expected behavior
the installer should make arturo executable?

Desktop (please complete the following information):

  • OS: Windows, + WSL 2 w ubuntu 2022.04

Additional context
Should be solveable by adding a "| chmod +x /home//.arturo/bin/arturo " into the onliner (untested)

@Ryton Ryton added the bug Something isn't working label Oct 5, 2023
@github-actions
Copy link

github-actions bot commented Oct 5, 2023

Thank you for submitting an issue! :)

@drkameleon
Copy link
Collaborator

I think your idea about chmoding the target binary makes sense.

The truth is this Curl-based script for installing Arturo were a nice, initial idea but in the end I haven't really fine-tuned them. I guess it's time I should! 😉

Copy link

stale bot commented Jun 2, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 2, 2024
Copy link

stale bot commented Oct 1, 2024

Closing issue as stale.

@stale stale bot closed this as completed Oct 1, 2024
@RickBarretto RickBarretto reopened this Jan 6, 2025
@stale stale bot removed the stale label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants