"Subversion repo imports are temporarily disabled"

[mabukhovsky]

Hi guys,

I'm trying to create bitbucket git repo from svn source and get this error message:

1. 19:47:51 svn import for: http://192.161.232.49/svn/xml
2. 19:47:51 Svn checkout failed: <class 'bitbucket.apps.async.tasks.ImportException'>: Subversion repo imports are temporarily disabled.

Any idea when this feature will be enabled again?

[Matthew Pease]

April 5, and it's still an option on the import page. Completely agree with David on every point.

[Jo Fowler]

Well that could basically make our migration decision easy.  I.e. not bit bucket :(

[Alastair Wilkes]

Hi there,

The Subversion importer has been disabled indefinitely.

Instead, we recommend converting your Subversion repository to a Git repository locally and then importing the new repository.

See this handy guide for steps on how to do it: https://www.atlassian.com/git/tutorials/migrating-overview

For clarity, we will update the repository import screen imminently to recommend this option.

Thanks,

Alastair
Bitbucket PM

[vintagedave]

Hi Alistair,

The documentation has been updated, but the actual import page has not.  Instead it still gives this error.

Can I persuade you that disabling allowing import from Subversion is a mistake? SVN is old and outdated, and many people - including myself - want to move repos to a more modern system, like git and mercurial. Doing this manually is a complicated process, with recommended steps including cloning the SVN repo locally, installing and using hgsubversion (the documentation for which is currently down), etc.

One of the benefits of Bitbucket is that it allows import from other repos, automatically, and allowing and helping people to move from SVN to a modern one would be very useful to your customers.

Regards,

David

[Gabriel_Marques]

100% Agreed.

My company is looking for a git repo, but we need to import our current base.

I was just exploring bitbucket as an option.. 

Well, not anymore.

[Atul Bothe]

I have similar problem, any idea when this will be enabled again?