3

我安装了svn2git以快速将 SVN 存储库转换为 GIT。我在另一台机器（Ubuntu 16.04）和不同的 SVN 存储库上尝试了转换过程，没有问题。

现在，我在 Linux Mint Cinnamon 上使用不同（但非常相似）的 SVN 存储库。

git clone https://my.git.com/repository.git
cd repository
svn2git svn://my.svn.com/repository --authors ../authors_transform.txt

.
.
.

error: unable to create symlink asp/layer/man/rep/onewith_totalmax_victory.php (File name too long)
read-tree -m -u -v HEAD HEAD: command returned error: 128

我已经阅读了 /home 加密可能性（作为文件长度限制），这不是我的情况。尝试触摸随机字符串

touch Etiam_tortor_est0_placerat_sit_amet_dolor_in0_ultricies_malesuada_nisi-_Aenean_et_urna_enim-_Vivamus_porta0_velit_et_pulvinar_fermentum0_urna_lacus_tempor_sapien0_et_laoreet_tellus_elit_nec_ligula-_Nulla_iaculis0_libero_eget_rutrum_mattis0_nisl_velit_vive

这是 256 个字符并创建文件。

如何处理？

编辑：问题也出现在 macOS Sierra 上。

4

3 回答 3

3

Conversion broke the symlink try this:

git clone --no-checkout https://my.git.com/repository.git
cd repository
git config core.symlinks false
git checkout <branch>
于 2016-12-01T22:16:31.203 回答
1

After all it seems it has been an issue with a specific file that was symlink and a file at the same time?

Anyways manually fixing the file in SVN and then performing the conversion fixed the issue.

于 2016-12-05T13:13:49.760 回答
0

svn2git您使用的工具git-svn在后台使用，因此它不适合“快速转换”SVN 存储库。

有很多称为svn2git的工具，可能最好的一个是来自https://github.com/svn-all-fast-export/svn2git的 KDE 工具。我强烈建议使用该svn2git工具。这是我所知道的最好的，并且在你可以用它的规则文件做什么方面非常灵活。

您使用的工具svn2git基于git-svn并且git-svn不是用于一次性转换存储库或存储库部分的正确工具。如果您想使用 Git 作为现有 SVN 服务器的前端，这是一个很棒的工具，但对于一次性转换，您不应该使用，git-svn但svn2git它更适合这个用例。

If you are not 100% about the history of your repository, svneverever from http://blog.hartwork.org/?p=763 is a great tool to investigate the history of an SVN repository when migrating it to Git.

Even though git-svn (or the wrong svn2git in your case) is easier to start with, here are some further reasons why using the KDE svn2git instead of git-svn is superior, besides its flexibility:

  • the history is rebuilt much better and cleaner by svn2git (if the correct one is used), this is especially the case for more complex histories with branches and merges and so on
  • the tags are real tags and not branches in Git
  • with git-svn the tags contain an extra empty commit which also makes them not part of the branches, so a normal fetch will not get them until you give --tags to the command as by default only tags pointing to fetched branches are fetched also. With the proper svn2git tags are where they belong
  • if you changed layout in SVN you can easily configure this with svn2git, with git-svn you will loose history eventually
  • with svn2git you can also split one SVN repository into multiple Git repositories easily
  • or combine multiple SVN repositories in the same SVN root into one Git repository easily
  • the conversion is a gazillion times faster with the correct svn2git than with git-svn

There are many reasons why git-svn is worse and the KDE svn2git is superior. :-)

于 2016-11-28T11:05:48.457 回答