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

How to repair a shallow clone (?)

From
Torsten Bögershausen <tboegi@web.de>
Date
Dec 6, 2014, 12:23 UTC
Message-ID
<5482F55F.1060008@web.de>

I share a bare repo with Sparkleshare which does an auto-synch. Now the synch had stopped, and trying to push to the central repo by hand gives this:

git push origin master fatal: protocol error: expected old/new/ref, got 'shallow 72fb4080921221293e28a97a0e8c78d6100c5186' fatal: The remote end hung up unexpectedly Counting objects: 4, done. Delta compression using up to 2 threads. Compressing objects: 100% (4/4), done. error: pack-objects died of signal 13 error: failed to push some refs to xxxxx

Both machines have Git >2.0.0
Is this a known issue/problem ?

I think I started to clone the repo in a shallow way (SparkleShare asked if I want to clone the complete history, and I probably answered "no" )

Is there a way to repair this situation ? (Except doing a complete re-clone ?)

Thanks for help
Next: Trần Ngọc Quân
Message 1 of 5 in “How to repair a shallow clone (?)”
  1. Torsten BögershausenDec 6, 2014
  2. Trần Ngọc QuânDec 7, 2014
  3. Philip OakleyDec 7, 2014
  4. Duy NguyenDec 7, 2014
  5. Torsten BögershausenDec 7, 2014

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.