Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

SVN Clean Up step error

I am completing the conversion preparing the branches (clean up step). When I run the java clean-git script (java -Dfile.encoding=utf-8-jar svn-migration-scripts.jar clean-git), I get the following error. I'm running the conversion in Windows.

Could not retrieve the config for the key: svn-remote.svn.url

Any ideas on where I went wrong?



6 answers

1 accepted

2 votes
Answer accepted

Issue was caused by cloning and changing the database before performing the clean up step. The clean up script is expecting SVN tags in the config file in .git folder. I went back to the original git svn converted repository and started over.

[svn-remote "svn"]
url = svn://localhost
fetch = MyRepo/trunk:refs/remotes/trunk
branches = MyRepo/branches/*:refs/remotes/*
tags = MyRepo/tags/*:refs/remotes/tags/*

authorsfile = c:/FooFolder/authors.txt

I decided not to migrate any branches, so the cleanup was giving me this error.

As a workaround, I simply added an empty "branches" key under [svn-remote "svn"] configuration section. Something like this:

[svn-remote "svn"]
	branches =

Works perfectly.

Works for me also. My svn repo didn't have any branches, just tags and a trunk, so no branches to migrate. I didn't specify --branches in the git svn clone command.

This also works for branches without tags, specify an empty tags key in the same configuration section

Our SVN repo has a structure like:






I used to following command for git clone

git svn clone --trunk=/trunk --branches=/branch --branches=/label --branches=/private --branches=/release --authors-file=authors.txt http://svn_repo_link_to_one_project_android AndroidAsGit

The command ended successfully without any issues.

On my local Computer, I could only see the trunk code has been checked out and the remaining branches are not checked out.

When I run the command below, I get the following issue Could not retrieve the config for the key: svn-remote.svn.url

java -Dfile.encoding=utf-8 -jar D:\GitRepository\svn-migration-scripts.jar clean-git

Here is my config file

    repositoryformatversion = 0
    filemode = false
    bare = false
    logallrefupdates = true
    symlinks = false
    ignorecase = true
    hideDotFiles = dotGitOnly
[svn-remote "svn"]
    url = http://svn base url
    fetch = MedKit/Android/trunk:refs/remotes/trunk
    branches = MedKit/Android/branch/*:refs/remotes/*
    branches = MedKit/Android/label/*:refs/remotes/*
    branches = MedKit/Android/private/*:refs/remotes/*
    branches = MedKit/Android/release/*:refs/remotes/*
    authorsfile = d:/NewGitRepository/authors.txt

Can any one suggest, how can I fix this issue.


yes and no.

Our SVN repo had a structure like:







So I've moved the trunk/, tags/, and branches/ to a new code.git, docproejct to a doc.git and I haven't decided what to do with the releases and data yet. The releases contains binary builds that we use to deploy our application (in lieu of a package manager). Internally we need to decide if we want to carry this over to git.

Ok looks like my particular problem I'm having is due to the fact that the repo I'm converting does not have branches and tags.

Does that mean you didn't have a typical SVN setup with Trunk, Branches, and Tags? Do you have trunk?

I'm having the same problem.

Error message is: Could not retrieve the config for the key: svn-remote.svn.branches

Migrating on Ubuntu 12.04; svn, version 1.6.17 (r1128011); git version

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

177 views 1 6
Read article

Atlassian Community Events