login
Header Space

 
 

git-svn bug?

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: git@vger.kernel.org <git@...>
Subject: git-svn bug?
Date: Wednesday, November 15, 2006 - 5:05 pm

I've got a repository I've converted over to git from svn.  (using  
git-svn.  since there's only been one branch, I figured I could skip  
git-svnimport).

For quite a while, all I did was fetch/rebase from the svn repository to  
my git repository; all of my own work was committed to the git repository;  
none of the changes were commited to the svn repository.

Then came the time to commit changes from my git repository to the svn  
repository.

Being somewhat cautious, I created an empty 'dummy' svn repository and  
familiarize myself with using git-svn to commit from git -> svn.

I ran:
git-svn fetch
git-svn rebase remotes/git-svn (already updated)
git-svn dcommit (to push my changes to the svn repository)

Everything seemed to work fine with the dummy repository.

Encouraged, I did the same with the 'real' repository, and received the  
following error:
(Using git 1.4.3.5, svn 1.4.0 on a Gentoo box)
fatal: Not a valid object name 92e2e0c50bbbacb0a3426b2c0f8b3e043eb4830a~1
32768 at /usr/lib64/perl5/5.8.8/Memoize.pm line 269

(using git 1.4.4, svn 1.3.0 on a SLES 9 SP3 box)
fatal: Not a valid object name 92e2e0c50bbbacb0a3426b2c0f8b3e043eb4830a~1
32768 at /usr/lib/perl5/5.8.3/Memoize.pm line 269

(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 had NFS mounted the git repository, so the SLES 9 was local the other  
two were NFS.  In any event, the error seems to be essentially identical  
on every platform I've tried.

Additionally, I had created three branches for the purpose of pushing my  
changes to svn:
master (used for my own development)
svn (created using git checkout -b svn remotes/git-svn -- basically only  
what is in svn)
merge (git checkout -b merge svn; git rebase master)

`git diff-tree merge master | wc -l` returns 0 (which I assume means no  
changes)
`git diff-tree svn merge | wc -l` returns 44 (again, I assume this means  
44 changes)

I couldn't find an object named  
"92e2e0c50bbbacb0a3426b2c0f8b3e043eb4830a~1" in .git/

Aside from my cluelessness, is there anything else wrong?
-- 
Troy Telford
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
git-svn bug?, Troy Telford, (Wed Nov 15, 5:05 pm)
Re: git-svn bug?, Seth Falcon, (Wed Nov 15, 6:33 pm)
Re: git-svn bug?, Troy Telford, (Wed Nov 15, 7:09 pm)
Re: git-svn bug?, Shawn Pearce, (Wed Nov 15, 6:37 pm)
Re: git-svn bug?, Seth Falcon, (Thu Nov 16, 11:32 am)
Re: git-svn bug?, Junio C Hamano, (Wed Nov 15, 5:43 pm)
Re: git-svn bug?, Troy Telford, (Wed Nov 15, 6:55 pm)
Re: git-svn bug?, Eric Wong, (Fri Nov 17, 4:55 am)
Re: git-svn bug?, Troy Telford, (Fri Nov 17, 5:17 pm)
Re: git-svn bug?, Eric Wong, (Sun Nov 19, 12:52 pm)
speck-geostationary