From: Justin Su <injustsu@gmail.com>
To: git@vger.kernel.org
Subject: Fetching upstream remote fails if repo was a blobless clone
Date: Fri, 1 Aug 2025 05:30:56 -0400 [thread overview]
Message-ID: <CAB=S_8+LMsSpnRWQZwK2Dj63WdcPy1vp+aJ=erDbf_aaPoU3cA@mail.gmail.com> (raw)
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)
```
git clone --filter=blob:none git@github.com:injust/delta
cd delta/
git remote add upstream git@github.com:dandavison/delta
git fetch upstream
```
What did you expect to happen? (Expected behavior) Fetch the upstream repo
What happened instead? (Actual behavior)
```
remote: Enumerating objects: 1578, done.
remote: Counting objects: 100% (776/776), done.
remote: Compressing objects: 100% (15/15), done.
remote: Total 1578 (delta 772), reused 761 (delta 761), pack-reused 802 (from 2)
Receiving objects: 100% (1578/1578), 2.67 MiB | 5.34 MiB/s, done.
Resolving deltas: 100% (1156/1156), completed with 356 local objects.
fatal: did not receive expected object 0020d54b979cc8cf59a13406f98bfe515b190559
fatal: fetch-pack: invalid index-pack output
```
Anything else you want to add: This only happens if a blobless clone
is performed
[System Info]
git version:
git version 2.50.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
libcurl: 8.6.0
zlib: 1.2.12
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
uname: Darwin 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 19:53:26
PDT 2025; root:xnu-11417.121.6~2/RELEASE_X86_64 x86_64
compiler info: clang: 16.0.0 (clang-1600.0.26.6)
libc info: no libc information available
$SHELL (typically, interactive shell): /usr/local/bin/fish
next reply other threads:[~2025-08-01 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 9:30 Justin Su [this message]
2025-08-02 9:32 ` Fetching upstream remote fails if repo was a blobless clone Jeff King
2025-08-02 18:02 ` Justin Su
2025-08-02 18:28 ` Justin Su
2025-08-02 19:31 ` Jeff King
2025-08-02 19:55 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAB=S_8+LMsSpnRWQZwK2Dj63WdcPy1vp+aJ=erDbf_aaPoU3cA@mail.gmail.com' \
--to=injustsu@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).