Re: Fetching upstream remote fails if repo was a blobless clone

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Aug 01, 2025 at 05:30:56AM -0400, Justin Su wrote:

> git clone --filter=blob:none git@xxxxxxxxxx:injust/delta
> cd delta/
> git remote add upstream git@xxxxxxxxxx:dandavison/delta
> git fetch upstream
> [...]

> ```
> 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
> ```

Hmm. I can't reproduce here, but I wonder if it is dependent on the
server-side repo state. E.g., if it depends on the fetch from the
upstream remote receiving a delta against a blob from origin. And that
might change if the server repacks, or even if there is another push.

Is it still happening for you?

-Peff




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux