I ran into this problem when I had identically-named subdirectories within branches or tags. For example, I had tags candidates/1.0.0 and releases/1.0.0, and this caused the documented error because subdirectory 1.0.0 appears within both candidates and releases. Per git-svn docs: When using multiple –branches or –tags, git svn does not automatically handle name collisions (for … Read more
git svn uses SVN commands directly and thus the internally saved password of SVN. Run the command: svn checkout –username user –password pass svn://server/repo and let SVN remember your password. If this does not work remove the saved SVN authentications: $HOME/.subversion/auth/svn.simple/* Then git svn clone will prompt you for the password.
I ended up having to delete the auth directory all together and allow Subversion to rebuild it for me. Nothing else seemed to work. For anyone who doesn’t know, the auth directory is in ~/.subversion (Mac/Linux).
Use rmdir argument or config parameter: –rmdir Only used with the dcommit, set-tree and commit-diff commands. Remove directories from the SVN tree if there are no files left behind. SVN can version empty directories, and they are not removed by default if there are no files left in them. git cannot version empty directories. Enabling … Read more
Consider the command git svn it has a similar log function than git log: git svn log it has the find-rev option (to retrieve the SVN revision from a SHA1 key) (introduced in git 1.6.0) I am not sure of you can combine those two options in one command line though. A script (a bit … Read more
Best way to work on a Subversion Repository via Git: git svn init -s https://svn.repo/app/ myrepo assuming that under https://svn.repo/app/ the repo contains the standard /trunk, branches and tags subdirectories Do a git svn fetch in myrepo until no more commits are fetched (may take quite some time and sometimes aborts under Windows). Checkout a … Read more
I had to open up the .git/config file and delete all the branches and tags entries under the svn-remote section and run the ‘git svn clone’ command for this error to go away. Apparently, if I run this command multiple times (usually stop and re-start from a revision), the branch/tag entries get added to the … Read more
Please don’t remove the .git/svn folder to fix this. It requires you to rebuild everything, it is annoying, it will take awhile (for the size of my repo several hours) and it is NOT NECESSARY. I found the right answer here and I’ve included it below. From the link: Inside the .git directory run the … Read more
take a look at this snipped from your error code: Authorization failed: OPTIONS of ‘https://<redacted>:2443/svn/LS/branches/PRODUCTION-SUPPORT-1/ls-policygen’: authorization failed: Could not authenticate to server: ignored NTLM challenge, rejected Basic challenge (https://<redacted>:2443) at /usr/local/libexec/git-core/git-svn line 943 specially at this part: Could not authenticate to server: ignored NTLM challenge It looks like your company also changed autentication methods too. … Read more
No. A git-svn clone converts the entire repository into git. SVN checkouts do not have the entire repository and so cannot be cloned from. This is the primary advantage of switching from SVN or CVS to a distributed system (like git).