git(1.8.3.1) push to an empty repository failed #3743

New Issue

GiteaMirror · 2025-11-02T05:23:54-06:00

GiteaMirror commented

2025-11-02 05:23:54 -06:00

Originally created by @lunny on GitHub (Aug 7, 2019).

On a client machine with git version 1.8.3.1

created a empty repository(No readme and others) on gitea(version 1.9.0)
git push -u origin master, then it returned

error: src refspec master does not match any.
error: failed to push some refs to 'https://xxxx/myname/myrepo.git'

Gitea error log is:

2019/08/07 16:25:44 routers/repo/http.go:430:serviceRPC() [E] Fail to serve RPC(upload-pack): exit status 128 - {[102 97 116 97 108 58 32 116 104 101 32 114 101 109 111 116 101 32 101 110 100 32 104 117 110 1
03 32 117 112 32 117 110 101 120 112 101 99 116 101 100 108 121 10] 0 0}

But with git 2.x, there is no error here.

Originally created by @lunny on GitHub (Aug 7, 2019). On a client machine with git version 1.8.3.1 1. created a empty repository(No readme and others) on gitea(version 1.9.0) 2. `git push -u origin master`, then it returned ``` error: src refspec master does not match any. error: failed to push some refs to 'https://xxxx/myname/myrepo.git' ``` Gitea error log is: ``` 2019/08/07 16:25:44 routers/repo/http.go:430:serviceRPC() [E] Fail to serve RPC(upload-pack): exit status 128 - {[102 97 116 97 108 58 32 116 104 101 32 114 101 109 111 116 101 32 101 110 100 32 104 117 110 1 03 32 117 112 32 117 110 101 120 112 101 99 116 101 100 108 121 10] 0 0} ``` But with git 2.x, there is no error here.

GiteaMirror added the issue/stale label 2025-11-02 05:23:54 -06:00

GiteaMirror closed this issue

2025-11-02 05:23:54 -06:00

GiteaMirror commented

2025-11-02 05:23:55 -06:00

@stale[bot] commented on GitHub (Oct 6, 2019):

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

@stale[bot] commented on GitHub (Oct 6, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:23:55 -06:00

@stale[bot] commented on GitHub (Oct 20, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Oct 20, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror commented

2025-11-02 05:23:56 -06:00

@zeripath commented on GitHub (Oct 20, 2019):

Likely fixed by #8476 in any case.

@zeripath commented on GitHub (Oct 20, 2019): Likely fixed by #8476 in any case.

GiteaMirror referenced this issue

2025-11-02 11:39:06 -06:00