git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Troy Telford" <ttelford.groups@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: git-svn bug?
Date: Wed, 15 Nov 2006 14:05:37 -0700	[thread overview]
Message-ID: <op.ti2svo0ozidtg1@rygel.lnxi.com> (raw)

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?
-- 

             reply	other threads:[~2006-11-15 21:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 21:05 Troy Telford [this message]
2006-11-15 21:43 ` git-svn bug? Junio C Hamano
2006-11-15 22:55   ` Troy Telford
2006-11-17  8:55     ` Eric Wong
2006-11-17 21:17       ` Troy Telford
2006-11-19 16:52         ` Eric Wong
2006-11-15 22:33 ` Seth Falcon
2006-11-15 22:37   ` Shawn Pearce
2006-11-16 15:32     ` Seth Falcon
2006-11-15 23:09   ` Troy Telford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.ti2svo0ozidtg1@rygel.lnxi.com \
    --to=ttelford.groups@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).