Launchpad itself

Re launchpad blender branch: bf-blender upstream switched from CVS to SVN

Asked by Keir Mierle

Upstream blender has made the switch from CVS (double-ugh) to svn (ugh). I tried to convince them to go bzr, but it didn't work. The new upstream blender url is: svn checkout https://svn.blender.org/svnroot/bf-blender/trunk/blender.

I'm not sure what's involved in switching from a CVS upstream to a SVN upstream. Perhaps a complete reconversion? Myself and and a few others in the community use the launchpad blender branch for much easier blender hacking.

Perhaps the best plan is to make a new branch bf-blender-svn and allow people who have outstanding branches off bf-blender to port the changes themselves. At the moment, I have an outstanding patch, but I've decided to start again so this is not an issue for me.

Let me know if you get this fixed, and I'll send word to the blender mailing lists.

Cheers,
Keir

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Christian Reis (kiko) said : 		#1

So to change an import is very simple -- just change the source details for the series and we will get the reimport done. Have you considered just trying that? I see that Urreta has done all the registration of blender so far; have you requested he do just that?

I'm curious as to why they didn't choose bzr at this point, btw. Do you have links or details on that discussion?

Revision history for this message
Keir Mierle (mierle) said : 		#2

> Christian Reis requested for more information:
> So to change an import is very simple -- just change the source details
> for the series and we will get the reimport done. Have you considered
> just trying that? I see that Urreta has done all the registration of
> blender so far; have you requested he do just that?

No, I am not involved with the Launchpad import.

> I'm curious as to why they didn't choose bzr at this point, btw. Do you
> have links or details on that discussion?

Basically like the old 'why don't people switch to linux from
windows'? discussion -- they were already very familiar with gforge,
gforge has svn integration, svn is rock solid and fast for enormous
repositories (of which blender is), and so they went with svn +
gforge.

It is my evil plan to switch them to bzr+launchpad sometime next year
after more of the performance work in bzr lands.

Keir

Revision history for this message
David Allouche (ddaa) said : 		#3

> So to change an import is very simple -- just change the source details for the series and we will get the reimport done.

When there is already an import running, as is the case for blender, it is not that simple. The old import must be cleared up by an operator, the old branch must be renamed away and its status must be set to Abandoned, some internal data must be moved away (that bit is not strictly needed, but it's good to keep our stuff tidy). That also means that the branch served on the bazaar.launchpad.net URL will be replaced by an unrelated (non-mergeable) branch, which can negatively affects users of that import. Finally, it's a similar, but subtly different, case than handling a host change for a import that is already running.

For all those reasons, changing a running import needs operator intervention, and filing a question here is the right thing to do. The process will be simplified in the future, but privileged action will still be needed in some cases.

Sorry for not acting on that issue so far. I will do it tomorrow.

Revision history for this message
David Allouche (ddaa) said : 		#4

Did the administrative things, and set the new import running. Now, let's see if it work.

Revision history for this message
Keir Mierle (mierle) said : 		#5

Thanks!

On 5/22/07, David Allouche <email address hidden> wrote:
> Your question #6651 on Launchpad Bazaar Integration changed:
> https://answers.launchpad.net/launchpad-bazaar/+question/6651
>
> David Allouche proposed the following answer:
> Did the administrative things, and set the new import running. Now,
> let's see if it work.
>
> _______________________________________________________________________
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/launchpad-bazaar/+question/6651/+confirm?answer_id=3
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/launchpad-bazaar/+question/6651
>

Revision history for this message
Christian Reis (kiko) said : 		#6

(When I said the change was simple, I meant from the user's perspective. I realize there is manual work that needs to be done on the backend.)

Revision history for this message
David Allouche (ddaa) said : 		#7

This was no a rant. The change was NOT simple from a user perspective, and that in this case, filing a question here was the proper thing to do.

Can you help with this problem?

Provide an answer of your own, or ask Keir Mierle for more information if necessary.

To post a message you must log in.