github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-25 07:56:03 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Windows new repo 500 #1545

New Issue
Closed
opened 2025-11-02 04:04:31 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 04:04:31 -06:00
Owner
Copy Link

Originally created by @wune5 on GitHub (Feb 19, 2018).

  • Gitea version (or commit ref): 1.4.0+rc1-8-gade1839
  • Git version: 2.15.1
  • Operating system: Windows 2012 R2
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

First new repo, mark "Initialize this repository with selected files and template".
Click create,see 500 err.
Log:
2018/02/19 19:42:40 [I] Log Mode: File(Info)
2018/02/19 19:42:40 [I] XORM Log Mode: File(Info)
2018/02/19 19:42:40 [I] Cache Service Enabled
2018/02/19 19:42:40 [I] Session Service Enabled
2018/02/19 19:42:41 [I] Git Version: 2.15.1
2018/02/19 19:42:41 [I] SQLite3 Supported
2018/02/19 19:42:41 [I] Run Mode: Production
2018/02/19 19:42:41 [I] First-time run install finished!
2018/02/19 19:43:10 [...routers/repo/repo.go:146 handleCreateError()] [E] CreatePost: initRepository: prepareRepoCommit: git clone: exec(4:initRepository(git clone): D:\gitserver\pyle\t.git) failed: exit status 128() stdout: stderr: Cloning into 'C:\Users\ADMINI~1\AppData\Local\Temp\3\gitea-t-542145100'...
error: cannot spawn sh: No such file or directory
fatal: unable to fork

  • Cloning into 'C:\Users\ADMINI~1\AppData\Local\Temp\3\gitea-t-542145100'...
    error: cannot spawn sh: No such file or directory
    fatal: unable to fork

Screenshots

Originally created by @wune5 on GitHub (Feb 19, 2018). - Gitea version (or commit ref): 1.4.0+rc1-8-gade1839 - Git version: 2.15.1 - Operating system: Windows 2012 R2 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description First new repo, mark "Initialize this repository with selected files and template". Click create,see 500 err. Log: 2018/02/19 19:42:40 [I] Log Mode: File(Info) 2018/02/19 19:42:40 [I] XORM Log Mode: File(Info) 2018/02/19 19:42:40 [I] Cache Service Enabled 2018/02/19 19:42:40 [I] Session Service Enabled 2018/02/19 19:42:41 [I] Git Version: 2.15.1 2018/02/19 19:42:41 [I] SQLite3 Supported 2018/02/19 19:42:41 [I] Run Mode: Production 2018/02/19 19:42:41 [I] First-time run install finished! 2018/02/19 19:43:10 [...routers/repo/repo.go:146 handleCreateError()] [E] CreatePost: initRepository: prepareRepoCommit: git clone: exec(4:initRepository(git clone): D:\gitserver\pyle\t.git) failed: exit status 128(<nil>) stdout: stderr: Cloning into 'C:\Users\ADMINI~1\AppData\Local\Temp\3\gitea-t-542145100'... error: cannot spawn sh: No such file or directory fatal: unable to fork - Cloning into 'C:\Users\ADMINI~1\AppData\Local\Temp\3\gitea-t-542145100'... error: cannot spawn sh: No such file or directory fatal: unable to fork ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/question label 2025-11-02 04:04:31 -06:00
GiteaMirror commented 2025-11-02 04:04:32 -06:00
Author
Owner
Copy Link

@wune5 commented on GitHub (Feb 19, 2018):

Thank lunny.xiao in QQ group 328432459.
His solution is add "LOCAL_ROOT_URL=http://127.0.0.1:3000" in custom/app.ini under "server".

@wune5 commented on GitHub (Feb 19, 2018): Thank lunny.xiao in QQ group 328432459. His solution is add "LOCAL_ROOT_URL=http://127.0.0.1:3000" in custom/app.ini under "server".
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1545
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?