threads / discuss / 23655

Import of svn rep has path issues

Subject: Import of svn rep has path issues

## tl;dr

3 messages between May 1, 2010 and May 4, 2010.

replies: 2people: 2as markdown or json

Paulo J. Matos· May 1, 2010, 13:45 UTC · lore

Hi all,

I just tried to import a svn project into git using git-svnimport. I followed: http://weblog.redlinesoftware.com/2008/2/24/converting-subversion-repositories-to-git

The line was: git-svnimport -C projname -r -v -A authors https://your-repo-host.com/projname

Interestingly some revisions resulted in a lot of errors with: 91: Unrecognized path: /main.cc

This seems to occur in the first revisions where I hadn't adopted a tree format of /branches, /tags, /trunk. On the other hand, git-svnimport returned 0 to the environment, so I would assume that those 'Unrecognized path' issues are just warnings and everything went fine. I would like to have some confirmation of this if possible and if these files were not imported into my new git rep, how can I solve these issues?

Thanks,

-- 
PMatos

Ulrich Spörlein· May 2, 2010, 08:15 UTC · re: Paulo J. Matos · lore

Re: Import of svn rep has path issues

On Sat, 01.05.2010 at 14:45:00 +0100, Paulo J. Matos wrote:

Show 19 quoted lines

> Hi all,
> 
> I just tried to import a svn project into git using git-svnimport.
> I followed:
> http://weblog.redlinesoftware.com/2008/2/24/converting-subversion-repositories-to-git
> 
> The line was:
> git-svnimport -C projname -r -v -A authors https://your-repo-host.com/projname
> 
> Interestingly some revisions resulted in a lot of errors with:
> 91: Unrecognized path: /main.cc
> 
> This seems to occur in the first revisions where I hadn't adopted a tree
> format of /branches, /tags, /trunk. 
> On the other hand, git-svnimport returned 0 to the environment, so I
> would assume that those 'Unrecognized path' issues are just warnings and
> everything went fine. I would like to have some confirmation of this if
> possible and if these files were not imported into my new git rep, how
> can I solve these issues?

Well, just look at your git-repo then and see if the logs indicate this file made it (I doubt it).

Please have a look at svn2git, which can take rules for what to do with specific paths at specific revisions. This should make it possible to go from

/ is master in git

to

/trunk is master in git

with little effort

Regards, Uli

Paulo J. Matos· May 4, 2010, 09:01 UTC · re: Ulrich Spörlein · lore

Re: Import of svn rep has path issues

Ulrich Spörlein <uqs@spoerlein.net> writes:

>
> Well, just look at your git-repo then and see if the logs indicate this
> file made it (I doubt it).
>

Indeed it didn't make it which is unfortunate.

> Please have a look at svn2git, which can take rules for what to do with
> specific paths at specific revisions. This should make it possible to go
> from
>

Thanks for the svn2git ref. My issue seems to be that my svn rep has been used for all sorts of stuff: docs, general files, source code and therefore I have actually never followed the branches/, tags/, trunk/ git-svnimport requires. Do you know if svn2git allows you to import an svn repository with all revisions as is even if they don't follow normal path conventions for software repositories?

Cheers,

-- 
PMatos