Git for Windows 2.41.0 stuck on push with gitea 1.19.3 #10959

Closed
opened 2025-11-02 09:23:17 -06:00 by GiteaMirror · 11 comments
Owner

Originally created by @MaxWaldorf on GitHub (Jun 4, 2023).

Description

With the latest git package, the push doesn't work anymore and stay stuck for ever at TOTAL xxxx.

Reverting to 2.40.1 solves the issue

Gitea Version

1.19.3

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

official dockerfile 1.19.3

Operating System

Linux

How are you running Gitea?

Official Dockerfile 1.19.3

Database

PostgreSQL

Originally created by @MaxWaldorf on GitHub (Jun 4, 2023). ### Description With the latest git package, the push doesn't work anymore and stay stuck for ever at TOTAL xxxx. Reverting to 2.40.1 solves the issue ### Gitea Version 1.19.3 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version official dockerfile 1.19.3 ### Operating System Linux ### How are you running Gitea? Official Dockerfile 1.19.3 ### Database PostgreSQL
GiteaMirror added the type/bug label 2025-11-02 09:23:17 -06:00
Author
Owner

@lunny commented on GitHub (Jun 4, 2023):

Linux or Windows?

@lunny commented on GitHub (Jun 4, 2023): Linux or Windows?
Author
Owner

@MaxWaldorf commented on GitHub (Jun 4, 2023):

windows client
linux server

@MaxWaldorf commented on GitHub (Jun 4, 2023): windows client linux server
Author
Owner

@eeyrjmr commented on GitHub (Jun 4, 2023):

This isn't related to git version

On my gentoo desktop
git -v git version 2.41.0

My alpine headless:
apk info gitea gitea-1.19.3-r0 installed size: 138 MiB

So this could be git-for-win v2.41.0. I can boot my work machine and upgrade git-for-win (it is v2.39.x) and see if the issue exists as : win-git-2.41 -> linux-gitea-1.19

@eeyrjmr commented on GitHub (Jun 4, 2023): This isn't related to git version On my gentoo desktop ` git -v git version 2.41.0 ` My alpine headless: `apk info gitea gitea-1.19.3-r0 installed size: 138 MiB ` So this could be git-for-win v2.41.0. I can boot my work machine and upgrade git-for-win (it is v2.39.x) and see if the issue exists as : win-git-2.41 -> linux-gitea-1.19
Author
Owner

@MaxWaldorf commented on GitHub (Jun 4, 2023):

Bear in mind that I am using the container provided by gitea.

There might be a matching git issue between server and client...

@MaxWaldorf commented on GitHub (Jun 4, 2023): Bear in mind that I am using the container provided by gitea. There might be a matching git issue between server and client...
Author
Owner

@eeyrjmr commented on GitHub (Jun 4, 2023):

Bear in mind that I am using the container provided by gitea.

There might be a matching git issue between server and client...

There shouldn't be. git is actually quite stable in terms of ABI with regards to data interchange

my alpine headless (running gitea-1.19.3) is also using git-2.40.1-r0. My gentoo desktop is using git-2.41

There might be a "bug" in git-for-win-2.41 and I can independently check shortly

@eeyrjmr commented on GitHub (Jun 4, 2023): > Bear in mind that I am using the container provided by gitea. > > There might be a matching git issue between server and client... There shouldn't be. git is actually quite stable in terms of ABI with regards to data interchange my alpine headless (running gitea-1.19.3) is also using git-2.40.1-r0. My gentoo desktop is using git-2.41 There might be a "bug" in git-for-win-2.41 and I can independently check shortly
Author
Owner

@eeyrjmr commented on GitHub (Jun 12, 2023):

Apologies for the delay...

Upgraded git-for-windows to 2.41.0 and cloning/pushing to to Gitea-1.19.3


 git -v
git version 2.41.0.windows.1

Something else is going on here.

@eeyrjmr commented on GitHub (Jun 12, 2023): Apologies for the delay... Upgraded git-for-windows to 2.41.0 and cloning/pushing to to Gitea-1.19.3 ``` git -v git version 2.41.0.windows.1 ``` Something else is going on here.
Author
Owner

@wxiaoguang commented on GitHub (Jul 9, 2023):

I am pretty sure the "stuck" is caused by incorrect log messages during startup.

It should have been fixed in 1.20/1.21

Feel free to reopen if there is still a problem

@wxiaoguang commented on GitHub (Jul 9, 2023): I am pretty sure the "stuck" is caused by incorrect log messages during startup. It should have been fixed in 1.20/1.21 Feel free to reopen if there is still a problem
Author
Owner

@MaxWaldorf commented on GitHub (Jul 13, 2023):

Sorry but 2.41.0.2 did not help either...

Works well with github... not with gitea... Happy to help, but don't know how to debug right now.

@MaxWaldorf commented on GitHub (Jul 13, 2023): Sorry but 2.41.0.2 did not help either... Works well with github... not with gitea... Happy to help, but don't know how to debug right now.
Author
Owner

@MaxWaldorf commented on GitHub (Jan 10, 2024):

No issues here anymore...

@MaxWaldorf commented on GitHub (Jan 10, 2024): No issues here anymore...
Author
Owner

@lunny commented on GitHub (Jan 10, 2024):

No issues here anymore...

How did you resolve the problem?

@lunny commented on GitHub (Jan 10, 2024): > No issues here anymore... How did you resolve the problem?
Author
Owner

@MaxWaldorf commented on GitHub (Jan 10, 2024):

The lastest git exe on windows and 1.21.x work so far

@MaxWaldorf commented on GitHub (Jan 10, 2024): The lastest git exe on windows and 1.21.x work so far
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10959