Import failures lp:~vcs-imports/gnomesword/trunk

It looks like the upstream moved their repository around in a way that would be hard for cscvs to track. Probably the easiest thing to do would be create a new import from https://gnomesword.svn.sourceforge.net/svnroot/gnomesword/trunk/, but this would not share any common history with the existing import branch -- would that be a problem?

2009/2/2 Michael Hudson <email address hidden>:
> Your question #59545 on Launchpad Bazaar Integration changed:
> https://answers.edge.launchpad.net/launchpad-bazaar/+question/59545
>
>    Status: Open => Answered
>
> Michael Hudson proposed the following answer:
> It looks like the upstream moved their repository around in a way that
> would be hard for cscvs to track.  Probably the easiest thing to do
> would be create a new import from
> https://gnomesword.svn.sourceforge.net/svnroot/gnomesword/trunk/, but
> this would not share any common history with the existing import branch
> -- would that be a problem?
>

That would be amazing. It will not cause a problem. There are 3 branches owned
by me which are stacked onto the old import but I think it will be easy for me
to re-stack them onto the new import when it will go live. After that the old
import will be save to delete (or you can just leave it there forever =D)

--
With best regards

Ледков Дмитрий Юрьевич

I set up a new import here: https://code.edge.launchpad.net/~vcs-imports/gnomesword/new-trunk

It'll take a while to import I guess, our servers are overloaded currently :/