Launchpad itself

Transitioning mixxx to bzr

Asked by Nick

The Mixxx developers are fed up with sourceforge and want to transition to launchpad. We have had launchpad tracking svn for a while and we want to make bzr our main branch.
I've read https://answers.edge.launchpad.net/launchpad-bazaar/+faq/26 and I assume that this is the right forum for requesting imports be disabled. When imports are disabled will trunk still be under ~vcs-imports or could it be moved to ~mixxxdevelopers? If it gets moved, will lp:mixxx still be a shortcut for it?

Also, the most recent imports have all failed with SSL errors, as you can see at https://code.launchpad.net/~vcs-imports/mixxx/trunk, so that needs to be worked around first. I know other projects have had this problem intermittently and all the solutions have involved a launchpad admin doing backend magic.

Thanks in advance!

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Michael Hudson-Doyle Edit question
Solved by:
Celso Providelo
Solved:
Last query:
Last reply:
Revision history for this message
Michael Hudson-Doyle (mwhudson) said : 		#1

I tell you, I'm going to get fed up with SF unless I can find some more reliable way of talking to their servers!!

The usual practice when making this transition is to grab a copy of the import branch, then push it up as a new branch (say lp:~mixxxdevelopsers/mixxx/trunk) and then making it the trunk branch by specifying it on this page:

https://edge.launchpad.net/mixxx/trunk/+linkbranch

That will make this new branch the one that lp:mixxx refers to. After that's done, the import branch can be deleted.

We hope you enjoy using Launchpad!

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

I've done the magic to get the branch updated. Let me know when you're ready to stop the import.

Revision history for this message
Nick (kousu) said : 		#3

So you mean I should:
$ bzr pull lp:mixxx #wait...
$ #go register lp:~mixxxdevelopsers/mixxx/trunk on the site
$ bzr push lp:~mixxxdevelopsers/mixxx/trunk #wait...
Is this any different than just pushing from my svn checkout (with bzr-svn installed)? Won't both methods take forever as the initial push pushes 2200 revisions?

Thank you for fixing the SF import.

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

You don't need to register the branch on the site first, you can just push to lp:~mixxxdevelopsers/mixxx/trunk.

It will take a while, yes, but not as long as it would with bzr-svn. Also, the ~vcs-imports branch is not made with bzr-svn, and so (as far as bzr knows) has no common ancestry -- you should pick the ~vcs-imports branch or a bzr-svn branch, you can't mix and match (sadly).

I can do the pull and push from a machine in the data centre, which will be much quicker than you doing it from wherever you are!

Revision history for this message
Nick (kousu) said : 		#5

I did the pull and push myself and it was pretty fast. However we're in the middle of a release cycle and we're not ready to suddenly switch out our VCS. It would be nice if we could run use bzr-svn to use both repos at once. I did try pushing to lp:mixxx but of course it failed, like you said it would. The only way to do this is to run `bzr push lp:mixxx` from my svn checkout and wait, right?

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

Yes, probably.

Revision history for this message
Nick (kousu) said : 		#7

Okay, thank you for being so helpful. We've decided that we're going to wait to our 1.6.2 release and then switch to bzr all at once, so no need to worry about bzr-svn troubles.

For simplicity, I'm just going to leave this ticket open for the day when we do decide to stop the imports.

Revision history for this message
Best Celso Providelo (cprov) said : 		#8

Nick,

I understand your point, but we'd rather not keep a support-request open any longer than it should be.

It looks like Michael has answered all your question and the migration is now blocked on your side; which is perfectly fine by all means.

If this is the current scenario would you mind marking this question as 'solved' for now (the historic data will remain available indefinitely for future reference) and only re-open it if you still having the same problem when you are ready to migrate ?

Revision history for this message
Nick (kousu) said : 		#9

Thanks Celso Providelo, that solved my question.