git svn clone fails with "Failed to strip path"

Question

I am using git in a shop that is all Subversion. When I check out a repo using

git svn clone -s --preserve-empty-dirs https://<subversion-server>/svn/<repo> <folder-name>

All seems well as the cloning process begins, but at some point during the process, git fails with

Failed to strip path '<path-to-some-file>' ((?^:^trunk(/|$)))

Anyone know what's wrong or how to fix this?

I found that re-running the git svn clone command seems to be a valid workaround when using git 2.7.3. It seems that git will continue just where it left off, similarly on network connection failures during git svn clone. — jotik
– jotik, Commented Mar 18, 2016 at 10:10

U007D · Accepted Answer · 2024-08-06 12:22:07Z

12

Searching the interwebs turned up both an explanation and advice on how to fix this (see step 4).

Note:

From v1.7.7 onward, Git has a --preserve-empty-dirs. Problem is, the damn thing's broken. If you try to use it as-is, the whole operation will likely just fail partway through. It has to be fixed.

But the advice may be dated, as it did not work for my installation (git 2.7.0). But now knowing the issue, I was able to find the offending line and apply the suggested fix:

The fix was made by changing the offending line in usr/lib/perl5/vendor_perl/5.22/Git/SVN/Fetcher.pm, line 163:

Change die "Failed to strip path... to print "Failed to strip path... and all will be well.

I hope that helps someone else out there as well.

edited Aug 6, 2024 at 12:22

answered Mar 4, 2016 at 1:53

U007D

6,4763 gold badges42 silver badges48 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

BenDavid Over a year ago

Performed the change from die to print. Ran this w/o option --no-metadata and was successful. Also ran the git svn process (with --no-metadata) and it continued to produce a remote repository. However the clone command output "done" and this, "warning: remote HEAD refers to nonexistent ref, unable to checkout." I was not able to locate a commit or any data in that clone. The underlying problem is not really explained. I recommend to restore the original 'die' command. When automating and running multiple conversions this could mask a problem that may only manifest when Murphy's Law applies.

foad322 Over a year ago

that worked for me in a jenkins container at path /usr/share/perl5/Git/SVN/Fetcher.pm

Collectives™ on Stack Overflow

git svn clone fails with "Failed to strip path"

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related