scalopus
scalopus

Reputation: 2720

Unable to determine upstream SVN information from HEAD history in some of git-svn commands

I have a problem with git svn

For this one, it occurs when try to git svn dcommit

Unable to determine upstream SVN information from HEAD history.
Perhaps the repository is empty. at C:\Program Files (x86)\Git/libexec/git-core\git-svn line 780.

I also have a problem with git svn info which show the same error message.

I try many ways as another topic provided but it never work. :(

I already try git fsck, git svn rebase -l also.

My repository is about 20,000 revisions. I fetched from http://localhost which sync from the original url, and after that, I change the url to the original one (in .git/config), after change I can run git svn fetch without problem. after that I follow this blog.

The problem still occurs.

Upvotes: 1

Views: 2068

Answers (1)

Marcus
Marcus

Reputation: 82

I've this use cause.

I have my project on Git marcusproject.

For some policies I have to manage SVN and Git toghether so I decided to use git svn.

Git svn works starting from SVN and for me It's a problem because I come from a git project.

So

  • Starting from Git I committed my project to my_svn_repo_url
  • Then in a new folder I run:

    git svn clone my_svn_repo_url (Note: After git svn clone you have to add again the remote)

    git remote add origin git@myurlgitrepo:/path/git/marcusproject.git

Now if I run

git svn info

all works fine.

    marco$ git svn info 

Path: 
 URL: http://myurl/svn/url/branches/project Repository 

Root: blablabla Repository UUID: 2e790b0d-f755-41c8-864a-d7ceaa3670a7 

Revision: 36 

Node Kind: directory Schedule: normal

 Last Changed Author: author 

Last Changed Rev: 36 

Last Changed Date: 2015-04-16 12:54:19 +0200 (Gio, 16 Apr 2015)

If I switch to a git branch already exists run git pull origin mybranch and the run git svn info i receive this error

Unable to determine upstream SVN information from HEAD history.
Perhaps the repository is empty.

But if I create my new branch starting from the new master git checkout -b newbranch all works fine.

So :

  1. push all your commit on git

  2. migrate to git svn (git svn clone)

  3. forget all your branches created before the "git svn clone"

  4. create new branch starting from new master

You will never see that error.

Enjoy

Upvotes: 1

Related Questions