Allow migration from Subversion #1882

New Issue

GiteaMirror · 2025-11-02T04:16:23-06:00

GiteaMirror commented

2025-11-02 04:16:23 -06:00

Originally created by @jmckenna on GitHub (Jun 6, 2018).

It would be nice to support migrating from an SVN repository. An example repository: https://svn.osgeo.org/osgeo/foss4g/

(background: the OSGeo foundation leveraged subversion for many years, and much information is still stored there)

Originally created by @jmckenna on GitHub (Jun 6, 2018). It would be nice to support migrating from an SVN repository. An example repository: https://svn.osgeo.org/osgeo/foss4g/ (background: the [OSGeo foundation](https://osgeo.org) leveraged subversion for many years, and much information is still stored there)

GiteaMirror added the type/question issue/stale labels 2025-11-02 04:16:23 -06:00

GiteaMirror closed this issue

2025-11-02 04:16:23 -06:00

GiteaMirror commented

2025-11-02 04:16:23 -06:00

@HaasJona commented on GitHub (Jun 7, 2018):

I suggest you follow this tutorial instead: https://www.atlassian.com/git/tutorials/migrating-overview

And then just import the resulting git repo into Gitea.

Automatically converting an SVN repository is not easily implemented, as you probably want to map SVN user names to longer Git user names and add e-mail addresses to them for example.

@HaasJona commented on GitHub (Jun 7, 2018): I suggest you follow this tutorial instead: https://www.atlassian.com/git/tutorials/migrating-overview And then just import the resulting git repo into Gitea. Automatically converting an SVN repository is not easily implemented, as you probably want to map SVN user names to longer Git user names and add e-mail addresses to them for example.

GiteaMirror commented

2025-11-02 04:16:23 -06:00

@lunny commented on GitHub (Jun 7, 2018):

I have ever converted all SVN repos to git repos by some scripts and then write a script via Gitea's API to import to Gitea.

@lunny commented on GitHub (Jun 7, 2018): I have ever converted all SVN repos to git repos by some scripts and then write a script via Gitea's API to import to Gitea.

GiteaMirror commented

2025-11-02 04:16:24 -06:00

@Morlinest commented on GitHub (Jun 9, 2018):

@jmckenna It is better to convert SVN repositories yourself, using git-svn for example (git svn clone). If you are using standard structure, it's very easy. There are almost always some steps you should do (e.g. resolving authors). Every SVN can be used in different way, so there are more ways to convert it (some of them can takes days to do so).

IMO Gitea should focus (at least for now) on storing git repositories and improve services around them, not converting another SCM types to git. But PR's are welcomed :)

@Morlinest commented on GitHub (Jun 9, 2018): @jmckenna It is better to convert SVN repositories yourself, using git-svn for example (git svn clone). If you are using standard structure, it's very easy. There are almost always some steps you should do (e.g. resolving authors). Every SVN can be used in different way, so there are more ways to convert it (some of them can takes days to do so). IMO Gitea should focus (at least for now) on storing git repositories and improve services around them, not converting another SCM types to git. But PR's are welcomed :)

GiteaMirror commented

2025-11-02 04:16:24 -06:00

@stale[bot] commented on GitHub (Jan 23, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 23, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:16:24 -06:00

@stale[bot] commented on GitHub (Feb 18, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 18, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:07:57 -06:00

[PR #2296] [MERGED] Only update needed columns when update user #16329

Sign in to join this conversation.