Launchpad itself

blender trunk import fails

Asked by Dietrich Bollmann

Hi,

Could you please have a look on the blender trunk import at https://code.launchpad.net/~vcs-imports/blender/trunk ?

It fails since more or less a month...

The problem probably is related to switching the blender tunk to the former branches/blender2.5 branch, as the switch was on Sat Sep 12, 2009, the same day the blender trunk import failed for the first time.

See http://lists.blender.org/pipermail/bf-committers/2009-September/024412.html and http://lists.blender.org/pipermail/bf-committers/2009-September/024439.html in thread http://lists.blender.org/pipermail/bf-committers/2009-September/thread.html#24412 .

Regards,

Dietrich

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
Paul Hummer (rockstar) said : 		#1

Both branches have been deleted.

Revision history for this message
Paul Hummer (rockstar) said : 		#2

Er, what I meant was, the branch should probably be deleted and re-imported. However, there are branches of this branch, and re-importing would break the other branch's ability to merge, etc.

It's up to you to decide what should be done here. Of course, re-importing might not actually fix the situation, but it definitely looks like it's related to the change made to trunk.

Revision history for this message
Wouter van Heyst (larstiq) said : 		#3

Could the branch be moved to blender-2.4 and others follow suit? I agree with Dietrich's assessment of the problem.

Revision history for this message
Dietrich Bollmann (diresu) said : 		#4

Hi Paul and Wouter :)

Is there no way to switch the depending branches to a new import? That would be sad news as the work in the branches would be lost again. This is the second time that the import has broken in just a few months and most people involved probably would not trust a new import either.

If it is not possible to switch the depending branches to a new import, it is probably safer to not delete them. At least if there is hope that some later launchpad version might be able to make the import work again.

By the way, the former blender 'trunk' was switched to 'branches/blender2.4'. Maybe the import would work again when changing the url to the new one?

If this works, it would make sense to rename the import to blender2.4. If this does not work I think it should better be renamed to something like blender-old000 and not blender2.4, as the latter one could be mistaken for an import of 'branches/blender2.4'.

After renaming the checkout I think, because of the correspondence of the names, it would make most sense to use https://code.launchpad.net/~vcs-imports/blender/trunk for reimporting the new blender trunk.

Best wishes, Dietrich

Can you help with this problem?

Provide an answer of your own, or ask Dietrich Bollmann for more information if necessary.

To post a message you must log in.