Volume XXII, number 280Wednesday, October 7, 2026Latest message 54 minutes ago

The Git List

News and archive of git@vger.kernel.org, since April 2005

Git for Windows Failing to Clone

2 messages between Jun 2, 2026 and Jun 3, 2026, from Dylan Carlyle, Johannes Schindelin.

Plain Markdown or JSON for tools and agents.

Dylan CarlyleJun 2, 2026, 11:31 UTC on lore

Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue):
Ran git clone user@ip_addres:repo
What did you expect to happen? (Expected behavior):
The repo to be cloned
What happened instead? (Actual behavior):

remote: Enumerating objects: 57873, done. remote: Counting objects: 100% (57873/57873), done. remote: Compressing objects: 100% (32002/32002), done. fatal: pack has bad object at offset 460179591: inflate returned 1 fatal: fetch-pack: invalid index-pack output

What's different between what you expected and what actually happened?
The clone never finishes on Windows.
Anything else you want to add:

Git version on the remote server is 2.47.3 This works fine from Linux but fails on Windows.

[System Info] git version: git version 2.54.0.windows.1 cpu: x86_64 built from commit: 2b8a3ab140826ac423c2845ef81d4c6ac4f7bf3c sizeof-long: 4 sizeof-size_t: 8 shell-path: D:/git-sdk-64-build-installers/usr/bin/sh rust: disabled feature: fsmonitor--daemon

-- 
Kind Regards,

Dylan Carlyle
REFTEK Systems, Inc.
Systems Administrator
Johannes SchindelinJun 3, 2026, 12:42 UTC in reply to Dylan Carlyle on lore

Re: Git for Windows Failing to Clone

Hi Dylan,
On Wed, 3 Jun 2026, Dylan Carlyle wrote:
Show 27 quoted lines
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
> 
> What did you do before the bug happened? (Steps to reproduce your issue):
> 
> Ran git clone user@ip_addres:repo
> 
> What did you expect to happen? (Expected behavior):
> 
> The repo to be cloned
> 
> What happened instead? (Actual behavior):
> 
> remote: Enumerating objects: 57873, done.
> remote: Counting objects: 100% (57873/57873), done.
> remote: Compressing objects: 100% (32002/32002), done.
> fatal: pack has bad object at offset 460179591: inflate returned 1
> fatal: fetch-pack: invalid index-pack output
> 
> What's different between what you expected and what actually happened?
> 
> The clone never finishes on Windows.
> 
> Anything else you want to add:
> 
> Git version on the remote server is 2.47.3
> This works fine from Linux but fails on Windows.

I guess that this is virtually identical to https://github.com/git-for-windows/git/issues/6265

Since it works from Linux, but not from Windows, I strongly suspect the problem to be related to that vexing 2GB/4GB problem induced by Git's continued use of `unsigned long` instead of `size_t`, which I am slowly (_very_ slowly) trying to address.

You can find out whether that effort might help you, by running `git repo structure` on the original repository (I'd expect a blob whose unpacked size is larger than 4GB).

Ciao, Johannes

Show 20 quoted lines
> 
> [System Info]
> git version:
> git version 2.54.0.windows.1
> cpu: x86_64
> built from commit: 2b8a3ab140826ac423c2845ef81d4c6ac4f7bf3c
> sizeof-long: 4
> sizeof-size_t: 8
> shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
> rust: disabled
> feature: fsmonitor--daemon
> 
> -- 
> Kind Regards,
> 
> Dylan Carlyle
> REFTEK Systems, Inc.
> Systems Administrator
> 
> 

Back to recent threads