Sourceforge FreeCAD svn import fails over http

Hi,

The VCS Import from Sourceforge svn for https://code.launchpad.net/~vcs-imports/freecad/trunk has been suspended after 5 import failures. The last successful import was on 09/25. All the failures end with this:

File "/srv/importd.launchpad.net/production/launchpad-rev-14071/bzrplugins/optional/svn/errors.py", line 149, in convert
    raise mapped_err
bzrlib.plugins.svn.errors.DavRequestFailed: A Subversion remote access command failed: REPORT of '/svnroot/free-cad/!svn/vcc/default': Could not read response body: Connection reset by peer (http://free-cad.svn.sourceforge.net)
Import failed:
Traceback (most recent call last):
Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 1.

We previously had 4 consecutive failures last month but the situation resolved itself without intervention.

This VCS import was set up back in 2009 over http. I've noted a previous answer where it is said that http is more reliable than https: https://answers.launchpad.net/launchpad/+question/170639

Considering our import's age, I'm guessing it's using CSCVS, while it seems new imports are done through bzr-svn which may be more reliable if I'm to believe this other answer: https://answers.launchpad.net/launchpad/+question/133001

I'm pasting the relevant comment below:
-----
Tim Penhey (thumper) said on 2010-11-07:

The underlying problem here is this one: Connection reset by peer (http://pio.svn.sourceforge.net)

The import is using CSCVS to import the code. This has known speed issues.

All new imports use bzr-svn, which is much faster and likely to be fine. The difference is that a new import using bzr-svn will not have common history with the existing import.
-----

Sorry for the long preamble, my question is specifically this:

- If our import is indeed CSVCS, what are the steps needed to change it to bzr-svn? Do we have to delete the existing imported branch and request a new one? Or can the existing one be switched somehow?
- What would the history loss entail on the bzr revision number? Would they be reset to smaller numbers than existing? Since we provide autobuild daily testing packages and use the bzr numbering in our package versioning, this could cause some inconvenience.

Thank you.