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

git svn fetch -> fatal: refs/remotes/trunk: not a valid SHA1

From
NKNicolas Kuttler <wp@nkuttler.de>
Date
Dec 12, 2010, 16:19 UTC
Message-ID
<20101212161928.GE30395@nicolaskuttler.de>
Hello,

I'm using git version 1.7.2.3 and get the "fatal: refs/remotes/trunk: not a valid SHA1" error while fetching from an svn repository.

$ mkdir test $ cd test $ git svn init -s http://svn.wp-plugins.org/zero-conf-mail $ git svn fetch -r246566

r246566 = 92e8abc50bf56cc1774e0e2688a280bc379a4817 (refs/remotes/tags/0.6.1) fatal: refs/remotes/trunk: not a valid SHA1 update-ref refs/heads/master refs/remotes/trunk: command returned error: 128

The problem seems to be that r246566 was created by a "git svn tag foo" command, fetching r246565 is works just fine. I didn't test if native svn tagging produces the same error but can do this if relevant. It could also be specific to the wordpress svn repository, I haven't tested that either.

Thanks,
Nicolas
P.S. Please CC me as I'm not on the list.

-- Nicolas Kuttler wp@nkuttler.de

http://www.nkuttler.de http://www.nicolaskuttler.de (deutsch)

Message 1 of 1 in “git svn fetch -> fatal: refs/remotes/trunk: not a valid SHA1”
  1. Nicolas KuttlerDec 12, 2010

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.