Launchpad itself

Can't see how to change the url for a vcs imports branch... ?

Asked by Justin Clift

Hi,

The source code for the Salasaga project used to be managed in three separate Subversion modules, each of which was represented in Launchpad.

These have now been merged into one, with a different name.

Not seeing how to update the Subversion URL of one to be correct (i.e. salasaga_ide -> salasaga), and delete the two left over.

?

Details
********

The SVN URL for this branch (trunk):

  https://code.launchpad.net/~vcs-imports/salasaga/salasaga_ide_trunk

    is presently:

  https://salasaga.svn.sourceforge.net/svnroot/salasaga/trunk/salasaga_ide

    and should be changed to:

  https://salasaga.svn.sourceforge.net/svnroot/salasaga/trunk/salasaga

These two branches have been merged into it, and should now be removed:

  https://code.launchpad.net/~vcs-imports/salasaga/salasaga_keycapture_trunk
  https://code.launchpad.net/~vcs-imports/salasaga/salasaga_screencapture_trunk

Regards and best wishes,

Justin Clift

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
Michael Hudson-Doyle Edit question
Last query:
Last reply:
Revision history for this message
Paul Hummer (rockstar) said : 		#1

We've deleted the the two other imports, but the trunk import will fail for a bit. We are currently experiencing difficulty in importing from Sourceforge, and we'll make sure the trunk is imported properly when we fix this issue.

Revision history for this message
Michael Hudson-Doyle (mwhudson) said : 		#2

The updated import isn't working, however, so I'll try to do some magic with rsync to get it up to date...

Revision history for this message
Michael Hudson-Doyle (mwhudson) said : 		#3

I tried to do my rsync magic and the import still failed:

http://launchpadlibrarian.net/19742402/salasaga-salasaga_ide_trunk-log.txt

The easiest thing to do at this point would be to dump the existing import and do a new one from scratch -- but this will break any existing branches you have made off the current import. Is that acceptable?

(and sorry for the delay in getting to this)

Revision history for this message
Justin Clift (justinclift) said : 		#4

Yep, go for it.

It's no stress in the slightest, as branch management for us is not done
with LP.

Regards and best wishes,

Justin Clift

--
Salasaga - Open Source GUI for
www.salasaga.org - eLearning creation

Revision history for this message
Michael Hudson-Doyle (mwhudson) said : 		#5

OK, import is going at https://code.edge.launchpad.net/~vcs-imports/salasaga/trunk.

As per usual, may take a while before it's done.

Can you help with this problem?

Provide an answer of your own, or ask Justin Clift for more information if necessary.

To post a message you must log in.