Skip to content

Allow migration from Subversion #4158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jmckenna opened this issue Jun 6, 2018 · 5 comments
Closed

Allow migration from Subversion #4158

jmckenna opened this issue Jun 6, 2018 · 5 comments
Labels
issue/stale type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@jmckenna
Copy link

jmckenna commented 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)

@HaasJona
Copy link

HaasJona commented 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.

@lunny
Copy link
Member

lunny commented 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.

@Morlinest
Copy link
Member

@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 :)

@lafriks lafriks added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Jun 12, 2018
@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Jan 23, 2019
@stale
Copy link

stale bot commented Feb 18, 2019

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

@stale stale bot closed this as completed Feb 18, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/stale type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

5 participants