git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Clone from shallow bundle bug

From
Duy Nguyen <pclouds@gmail.com>
Date
Apr 1, 2015, 09:55 UTC
Message-ID
<CACsJy8C0wMFiPw1thSWN-dPVW+9N=JXDsy_HFCj=Oyu2rf40eg@mail.gmail.com>
In-Reply-To
<551B0D37.5070407@ubuntu.com>
On Wed, Apr 1, 2015 at 4:10 AM, Phillip Susi <psusi@ubuntu.com> wrote:
Show 8 quoted lines
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I made a shallow clone of my repo, then used git bundle create to pack
> it all into a bundle file, then cloned from that bundle.  The initial
> shallow clone has a .git/shallow file that identifies it as a shallow
> clone ( and I guess keeps things from complaining about the missing
> history ), but the the repo cloned from the bundle does not,

You made me worry a bit. We have checks in clone and fetch to make sure the result is "good" (i.e. gitk should not complain, clone/fetch should report it instead). Unfortunately I tested and it seemed to work as expected (i.e. clone fails)

$ LANG=C ./git clone ./shallow.bundle shallow2 Cloning into 'shallow2'... Receiving objects: 100% (2813/2813), 5.33 MiB | 0 bytes/s, done. Resolving deltas: 100% (250/250), done. Checking connectivity... error: Could not read 50a3ba22454e2989424d5de489de9c0f68fed5ec fatal: Failed to traverse parents of commit c73a8a63134734ddf7077d09355a10a0077ed2ca fatal: remote did not send all necessary objects

> so gitk
> run in that clone complains about not being able to find the objects
> referenced by the oldest commit in the repo.
-- 
Duy
Previous: Phillip SusiNext: Phillip Susi
Message 11 of 16 in “Clone from shallow bundle bug”
  1. Phillip SusiMar 31, 2015
  2. Junio C HamanoMar 31, 2015
  3. Phillip SusiApr 1, 2015
  4. Junio C HamanoApr 1, 2015
  5. Duy NguyenApr 1, 2015
  6. Phillip SusiApr 1, 2015
  7. Junio C HamanoApr 1, 2015
  8. Duy NguyenApr 2, 2015
  9. Duy NguyenApr 2, 2015
  10. Phillip SusiApr 2, 2015
  11. Duy NguyenApr 1, 2015
  12. Phillip SusiApr 1, 2015
  13. Duy NguyenApr 1, 2015
  14. Phillip SusiApr 1, 2015
  15. Duy NguyenApr 1, 2015
  16. Phillip SusiApr 1, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.