What did you do before the bug happened? (Steps to reproduce your issue)
- I was migrating an SVN repository to Git using:
git svn clone <my-svn-repo> --stdlayout --authors-file=C:\path\to\my-authors-file.txt --preserve-empty-dirs .
What did you expect to happen? (Expected behavior)
- I expect the entire process to succeed without errors.
When unavoidable errors do happen, I expect the error message to be helpful, give a clear description of what the underlying problem is, and how to solve it.
What happened instead? (Actual behavior)
- The migration failed with the folowwing error:
r2814 = 1ecf20e2d14b45ee517b56f5f51b406801e9869b (refs/remotes/origin/trunk)
Found possible branch point: https://<my-svn-repo> => https://<my-svn-repo>/branches/<my-branch-name>, 2814
W: Refspec glob conflict (ref: refs/remotes/origin/trunk):
expected path: branches/trunk
real path: trunk
Continuing ahead with trunk
W: Refspec glob conflict (ref: refs/remotes/origin/trunk):
expected path: branches/trunk
real path: trunk
Continuing ahead with trunk
Initializing parent: refs/remotes/origin/<my-branch-name>@2814
Use of uninitialized value $args[2] in join or string at C:/Program Files/Git/mingw64/share/perl5/Git.pm line 1655.
Use of uninitialized value $_[3] in exec at C:/Program Files/Git/mingw64/share/perl5/Git.pm line 1681.
fatal: Not a valid object name
ls-tree -z --name-only data/OVK/: command returned error: 128
What's different between what you expected and what actually happened?
- The process failed instead of succeeding, and the error was incredibly unhelpful, and seems like a bug in Git.pm.
Anything else you want to add:
Before this happened, another error happened first, which may or may not be related:
r1126 = 9d5f073cfcac00b9d8586923da4d045699244749 (refs/remotes/origin/trunk)
Failed to strip path 'src/Lijsten/.gitignore' ((?^:^trunk(/|$)))
This also is not a very helpful error, as it gives no indication of *why* it failed to 'strip the path' (strip it of what, anyway?), nor why it failed on this particular commit.
Restarting the process by rerunning the same 'git svn clone' command seemed to 'fix' the problem by just continuing the process (which begs the question why the process aborted itself in the first place. Couldn't it just have continued?)
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.49.0.windows.1
cpu: x86_64
built from commit: cca1f38702730b35f52c29efd62864b85e85ddcc
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.12.1
OpenSSL: OpenSSL 3.2.4 11 Feb 2025
zlib: 1.3.1
uname: Windows 10.0 22631
compiler info: gnuc: 14.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
C2 - Restricted use
