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

[BISECTED] git-svn: "Failed to read object ..." during clone

From
Björn Steinbrink <b.steinbrink@gmx.de>
Date
May 28, 2008, 03:01 UTC
Message-ID
<20080528030128.GA28904@atjola.homenet>
Hi Adam,

when cloning the SVN repository at svn://svn.debian.org/estron/ git-svn bails out with: Failed to read object e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 at /usr/local/bin/git-svn line 3195, <GEN36> line 645.

Bisection led to:
ffe256f9bac8a40ff751a9341a5869d98f72c285 is first bad commit
commit ffe256f9bac8a40ff751a9341a5869d98f72c285
Author: Adam Roben <aroben@apple.com>
Date:   Fri May 23 16:19:41 2008 +0200
    git-svn: Speed up fetch
    
    We were spending a lot of time forking/execing git-cat-file and
    git-hash-object. We now maintain a global Git repository object in order to use
    Git.pm's more efficient hash_and_insert_object and cat_blob methods.

I can reliable reproduce the problem using this command: git svn clone -r215:230 svn://svn.debian.org/estron/trunk

$ git --version git version 1.5.6.rc0.13.g2d392 $ git svn --version git-svn version 1.5.6.rc0.13.g2d392 (svn 1.4.6)

Björn
Next: Junio C Hamano
Message 1 of 4 in “[BISECTED] git-svn: "Failed to read object ..." during clone”
  1. Björn SteinbrinkMay 28, 2008
  2. Junio C HamanoMay 28, 2008
  3. Sam VilainMay 28, 2008
  4. Björn SteinbrinkMay 28, 2008

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.