Sourcetree for mac是 Windows 和Mac OS X 下免费的SVN、Git 客户端，同时也是Mercurial和Subversion版本控制系统工具。Sourcetree for mac支持创建、克隆、提交、push、pull 和合并等操作。SourceTree拥有一个精美简洁的界面，大大简化了开发者与代码库之间的Git操作方式，这对于那些不熟悉Git命令的开发者来说非常实用。. Sourcetree is a free Git desktop client for developers on Windows.Say goodbye to the command line and use the full capabilities of Git through Sourcetree’s beautifully simple interface (and stop being jealous of what your Mac friends are using). After entering a Subversion URL in the Clone Repository source box, when SourceTree prompts you for the authentication details the spinning beachball cursor appears and the application freezes. This issue may occur the first time you authenticate against a Subversion URL, when the username is not known in advance. The svn diff command has a switch -diff-cmd to allow an external differencing engine to be used. This will be leveraged to used LVComare to operate on vis. To use LVCompare.exe with subversion in the command line, first add 'C:Program FilesNational InstrumentsSharedLabVIEW Compare' to your system PATH variable (this allows the command.

Use SubGit to make a one-time conversion between the local SVN repository and a new local Git repository. Push the new Git repository to a new upstream repository hosting service. But if the SVN repository is still active, then you would need to use git svn, as described in this article, in order to do git svn fetch/git svn dcommit.

Question or issue on macOS:

I’m using OSX and want get a svn repo into a local git repo using sourcetree.

When I add a bookmark using sourcetree using SVN URL, thus sourcetree knows it’s a SVN url, but when I click the clone button, it reports an error like following:

I don’t how to get it through. Can anyone give me a pointer on how to do this?

How to solve this problem?

Solution no. 1:

I hit this missing SVN/Core.pm issue recently with el capitain.

Desi tv. Fix I used was from Paul Schreiber’s blog :

Commenters below, say this worked on sierra and high sierra too.

Solution no. 2:

Or, if you don’t have Xcode, just CommandLineTools (this is on ElCapitan 10.11.6): The amazon rainforest for kids.

If you previously linked some older version or just made a mistake so it gives you: File exists, then you should first do

for whichever file was reported as already existent, of course.

EDIT Dir doesn’t exist: (suggested by @rogeriopradoj)

EDIT Sierra:
After upgrading to Sierra I lost CommandLineTools, so I just had to reinstall it and everything was back to normal.
This will prompt you to install just the CommandLineTools, not the whole XCode.

xcode-select --install

Hope this helps someone 🙂

Solution no. 3:

In my case, it is because different versioned perl was installed by brew as dependency of some formula, and override the system’s default version.

So the resolution for me is to relieve the overridden as described following.

when type which perl and perl -v, I find it not the system default version:

which should be v5.18.2 according to the git svn error messages.

I guess it is because the different versioned perl was installed by brew as dependency of some formula, and override the system default version.

Svn To Git Migration

To prove it, try to move /usr/bin before /usr/local/bin in $PATH, then perl was fallback to the system’s default version:

Sourcetree Equivalent For Svn

and perl -V list the @INC just satisfy the Can't locate SVN/Core.pm in @INC requirements:

type git svn and everything works well!

Solution no. 4:

Plus to the highest answer,
If you are using souceTree, simply paste command line may not work immediately.
In that case, you may need to check git used in your sourceTree, which should be set as System git.

Solution no. 5:

Sourcetree Won't Open Windows 10

Xcode 11.4 no longer includes SVN/Core.pm in its Perl bindings!

If you’ve never installed the commandline tools and Xcode 11.4 is the first version you’ve run you will see this issue. Running xcode-select --install returns error: command line tools are already installed, use “Software Update” to install updates, which is accurate but non-obvious that your installed commandline tools differ from what you would get if installed outside of Xcode 11.4. The solution is to first remove these, then install the commandline tools using xcode-select.

Solution no. 6:

Thanks Marko, I did find that on ElCapitan 10.11.3 I had to symlink to a different area. Not sure why, but it works.

Solution no. 7:

I got the same issue on Macos Mojave 10.14.1. Because I used the built-in version of git, and it’s too lower(2.19.0). I fixed it by upgrade git to the latest version(2.21.0), and I found 2.19.1 also has no this issue.

Solution no. 8:

The solution for me was to delete the password entry in the OSX key ring app, and have git svn re-create it. My key entry has been created earlier (by svn I suppose), and it seems that git cannot use this key entry (nor fix it nor add a second one).

The long story: I noticed that when unsing “system git” in SourceTree, there seemed to be a problem storing the credentials. When I entered the same git command (that SourceTree is issuing) on the command-line, git kept prompting me for my password each time.

Then I found https://stackoverflow.com/a/39800112/580672

If you are interested, my setup was:

No Xcode, only Command-Line tools (so I adapted the paths as mentioned in a post above ( https://paulschreiber.com/blog/2015/11/09/fixing-git-svn-on-os-x-el-capitan/comment-page-1/#comment-437843 )
Homebrew has svn and perl installed

I had tried with no success:

“embedded git” (yields the @INC error)
“system git” (different error: “Username: Use of uninitialized value $ret in chomp at /usr/local/Cellar/git/2.21.0/share/perl5/Git.pm line 596.”)
put usr/bin in front of my PATH as suggested above
force-uninstalled perl in homebrew

All without success. The solution was system git and the key entry, as stated above.

Solution no. 9:

I’ve found that the best solution is to expand the list of directories in @INC using an export

Referenced from: https://perlmaven.com/how-to-change-inc-to-find-perl-modules-in-non-standard-locations

Solution no. 10:

Manage to fix the same issue by changing the first line in /usr/local/Cellar/git/2.29.2/libexec/git-core/git-svn
to
#!/usr/local/bin/perl

Sourcetree For Svn