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

Endianness bug in git-svn or called component?

From
NFNathaniel W Filardo <nwf@cs.jhu.edu>
Date
Dec 4, 2009, 17:44 UTC
Message-ID
<20091204174458.GV17192@gradx.cs.jhu.edu>
On this machine,

mirrors hydra:/tank0/mirrors/misc% uname -a FreeBSD hydra.priv.oc.ietfng.org 9.0-CURRENT FreeBSD 9.0-CURRENT #13: Sat Nov 14 19:40:25 EST 2009 root@hydra.priv.oc.ietfng.org:/systank/obj/systank/src/sys/NWFKERN sparc64

attempting to fetch from an svn source yields the following error:
rs hydra:/tank0/mirrors/misc% git svn init -s https://joshua.svn.sourceforge.net/svnroot/joshua test-joshua
Initialized empty Git repository in /tank0/mirrors/misc/test-joshua/.git/                                       
mirrors hydra:/tank0/mirrors/misc% cd test-joshua                                                               
mirrors hydra:/tank0/mirrors/misc/test-joshua% git svn fetch
        A       scripts/distributedLM/config.template       
[...]
        A       build.xml
r1 = fe84a7d821ec6d92da75133ac7ad1deb476b6484 (refs/remotes/trunk)
error: index uses  extension, which we do not understand
fatal: index file corrupt
write-tree: command returned error: 128

Even on previously initialized and fetched git-svn repos, "git svn fetch" produces the same response.

This is the same symptom as an older bug, but I have not attempted to track down what's going wrong this time in hopes that somebody more familiar can fix it faster; see http://kerneltrap.org/mailarchive/git/2006/5/28/205750/thread#mid-205750 .

If there's anything more that would be helpful to know, please just ask.

Thanks. --nwf;

Next: Andreas Schwab
Message 1 of 9 in “Endianness bug in git-svn or called component?”
  1. Nathaniel W FilardoDec 4, 2009
  2. Andreas SchwabDec 4, 2009
  3. Nathaniel W FilardoDec 4, 2009
  4. Nathaniel W FilardoDec 18, 2009
  5. [RESEND] [PATCH] Endianness bug in index cache logicNathaniel W Filardo, Dec 27, 2009
  6. Erik Faye-LundDec 27, 2009
  7. Nathaniel W FilardoDec 27, 2009
  8. Junio C HamanoDec 27, 2009
  9. Tomas CarneckyDec 27, 2009

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.