nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SVN Clean Up step error

Rick Fisher

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?

Thanks

Rick

Accepted answers

Rick Fisher

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/*

[svn]
authorsfile = c:/FooFolder/authors.txt

All comments

Duncan Greer

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 1.7.9.5

Rick Fisher

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

[svn]
authorsfile = c:/FooFolder/authors.txt

Duncan Greer

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.

Rick Fisher

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

Duncan Greer

yes and no.

Our SVN repo had a structure like:

trunk/

tags/

branches/

releases/

docproject/

data/

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.

Neeme Praks1

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.

Kenny MacLeod

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.

Sarfaraz Madhia

Our SVN repo has a structure like:

trunk/

branch/

label/

release/

private/

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 \GitRepository\svn-migration-scripts.jar clean-git

Here is my config file

[core]
   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/*
[svn]
   authorsfile = d:/NewGitRepository/authors.txt

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

Girgis Ghattas

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