Skip to content

SCRIPT_TYPE "bash" is not on the current PATH #20580

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

Closed
jarvis0325 opened this issue Aug 1, 2022 · 2 comments
Closed

SCRIPT_TYPE "bash" is not on the current PATH #20580

jarvis0325 opened this issue Aug 1, 2022 · 2 comments
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@jarvis0325
Copy link

Description

v1.16.7 > v1.17.0

2022/08/01 10:35:05 ...etting/repository.go:289:newRepository() [W] SCRIPT_TYPE "bash" is not on the current PATH. Are you sure that this is the correct SCRIPT_TYPE?

How to fix this warring ?

Gitea Version

v1.17.0

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

img

Git Version

git version 2.34.1.windows.1

Operating System

windows

How are you running Gitea?

exe gitea.exe

Database

PostgreSQL

@eeyrjmr
Copy link
Contributor

eeyrjmr commented Aug 1, 2022

I can confirm this. Unsure if this is just a warning or related to a slowdown in startup noticed (windows only)

@eeyrjmr
Copy link
Contributor

eeyrjmr commented Aug 1, 2022

Running doctor shows:

[7] Check if SCRIPT_TYPE is available

  • [C] ScriptType ""bash"" is not on the current PATH. Error: exec: "bash": executable file not found in %PATH%
    ERROR

So I think this is the issue. Adding C:\Program Files\Git\bin\bash.exe to %PATH% makes this go away and doctor reports all is ok

@noerw noerw added type/question Issue needs no code to be fixed, only a description on how to fix it yourself. and removed type/bug labels Aug 1, 2022
@lunny lunny closed this as completed Mar 8, 2023
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

4 participants