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

Re: git-svn bug?

From
EWEric Wong <normalperson@yhbt.net>
Date
Nov 17, 2006, 08:55 UTC
Message-ID
<20061117085509.GA29644@localdomain>
In-Reply-To
<op.ti2xykijzidtg1@rygel.lnxi.com>
Sorry for the late replies, I've been caught up with other things.
Troy Telford <ttelford.groups@gmail.com> wrote:
Show 14 quoted lines
> On Wed, 15 Nov 2006 14:43:30 -0700, Junio C Hamano <junkio@cox.net> wrote:
> 
> >"Troy Telford" <ttelford.groups@gmail.com> writes:
> >
> >>(using git 1.4.4, svn 1.3.1 on a SLES 10 box)
> >>fatal: Not a valid object name  
> >>92e2e0c50bbbacb0a3426b2c0f8b3e043eb4830a~1
> >>32768 at /usr/lib/perl5/5.8.8/Memoize.pm line 269
> >>...
> >>I couldn't find an object named
> >>"92e2e0c50bbbacb0a3426b2c0f8b3e043eb4830a~1" in .git/
> >
> >Troy, do you have object 92e2e0c5?  Is it a root commit (i.e. a
> >commit that does not have a parent)?

dcommit expects to be run on a git-svn fetch-ed HEAD that is linear superset of remotes/git-svn. That is: remotes/git-svn..HEAD should (ideally) contain no merges, and no root commits. git-svn currently does no checking for root commits, but it should.

Show 12 quoted lines
> I'll have to admit I'm stabbing in the dark on how to get the correct  
> answer this, but here goes:
> 
> * `git cat-file -t 92e2e0...` returns 'commit'
> * 'git cat-file -p 92e2e0...` returns: (minus the header/footer asterisks)
> *********************************************
> tree 4b825dc642cb6eb9a060e54bf8d69288fbee4904
> author unknown <unknown> 961088898 +0000
> committer unknown <unknown> 961088898 +0000
> 
> New repository initialized by cvs2svn.
> *********************************************

This commit is missing the git-svn-id: line at the bottom. If you simply left it out (private svn repository info), can you check that the URL in this line is actually for the SVN repository you want to commit to?

It seems like your usage of dcommit would actually cause the issue you're experiencing to be triggered on the dummy repository, and not the real one. My other guess would be that you somehow merged commits from your dummy svn repo into your master branch.

Previous: Troy TelfordNext: Troy Telford
Message 4 of 10 in “git-svn bug?”
  1. Troy TelfordNov 15, 2006
  2. Junio C HamanoNov 15, 2006
  3. Troy TelfordNov 15, 2006
  4. Eric WongNov 17, 2006
  5. Troy TelfordNov 17, 2006
  6. Eric WongNov 19, 2006
  7. Seth FalconNov 15, 2006
  8. Shawn PearceNov 15, 2006
  9. Seth FalconNov 16, 2006
  10. Troy TelfordNov 15, 2006

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.