blender import fails: cscvs.cmds.totla.ValidationFailed: directories differ, Import failed...

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Hi,

The import of the blender sources still doesn't work...

...Is it OK to start another blender branch for my own blender experiments?

Thanks,

Dietrich

Yeah, I suggest doing exactly that. Do a new import and let's see what happens to it! Do you need the old one renamed?

Hi Christian,

As other peoples projects might depend on the old one and I am not sure how much
time I will find to spend on the new branch I rather would prefer to do an import using
some other name and to leave the old one untouched.

So there is no problem to have more than one blender import of the same project
on launchpad?

Are there some general guidelines for naming imports?

If there are no general guidlines and it is ok to have several imports, how about calling
 the new import '<my user name>-blender-trunk' and branches based on this
'<my user name>-blender-<some feature>'. So other people could use their own
user name for their own blender import in order to not depend on me if some similar
import problem occurs in the future?

Thanks for your answer :)

Dietrich

There's no problem at all in keeping both imports running and you are a wise man for remembering people may be using the old one. The only thing I find a bit odd is that you suggest having an import prefixed by your username -- isn't this a general import of trunk?

Yes, it would be!

The idea to use my username was to shortcut something like:
"This is nothing more than the humble base of stupid diresu's blender experiments"
but you are right, it sounds like "This is glorious diresu's creation called blen***" which
is of course not what I intent at all!

If I would just call it "blender-trunk" I would rob away some other nice general
name for a blender import and some other user who needs to import it
again would have to invent yet another name.

How about giving it a number: 'blender-import-000' so the next person
could call his import 'blender-import-000' ?

Thanks and best wishes, Dietrich

Right, a trunk is a trunk - and if there are trunk1, trunk2 ... and they all import
the same sources, it doesn't make sense.

I didn't know that it is so simple to rename an import and thougth that
everybody would have to wait for the "owners" of the old import to fix
the problem.

Is it as simple for a branch of some import to switch to a new import?

Thanks for your help :)

Dietrich

Thanks Christian Reis, that solved my question.

On Mon, Nov 10, 2008 at 03:13:41PM -0000, Dietrich Bollmann wrote:
> I didn't know that it is so simple to rename an import and thougth that
> everybody would have to wait for the "owners" of the old import to fix
> the problem.
>
> Is it as simple for a branch of some import to switch to a new import?

No, and I think it's essentially because of the disk layout of the
imported code. Sometimes it's easy to fix it, but sometimes it's not.
--
Christian Robottom Reis | [+55 16] 3376 0125 | http://launchpad.net/~kiko
                        | [+55 16] 9112 6430 | http://async.com.br/~kiko

Good morning Christian :)

It looks like the new import doesn't work either :(

There is no link to any log file though as there was for the old import.
Is there some other way to check why the new import didn't work either?

By the way - for some strange reason I seem to be unable to find the launchpad
sources themselves. I suppose they are somewhere on launchpad :) but I seem to
be unable to find them.

Could you send me the link?

I thought about installing launchpad locally in order to be able to find out why
the import doesn't work. May be I could fix it and supply a patch. Or maybe not:
I couldn't pay my last rent and probably rather should rise the priority of the task
concerned with fixing the latter problem :(

Take care, Dietrich

On Tue, 11 Nov 2008 15:40:00 Dietrich Bollmann wrote:
> Question #48252 on Launchpad Bazaar Integration changed:
> https://answers.launchpad.net/launchpad-bazaar/+question/48252
>
> Dietrich Bollmann posted a new comment:
> Good morning Christian :)
>
> It looks like the new import doesn't work either :(
>
> There is no link to any log file though as there was for the old
> import. Is there some other way to check why the new import didn't
> work either?
>
> By the way - for some strange reason I seem to be unable to find the
> launchpad sources themselves. I suppose they are somewhere on
> launchpad :) but I seem to be unable to find them.

The code that actually does the import is cscvs, and that can be found
at https://edge.launchpad.net/launchpad-cscvs. We have some wrapper
scripts that go around cscvs, but if you can get cscvs importing the
branch, then Launchpad will be able to as well.

Hi Tim,

Thank you! I will have a look on it. Not sure when though :)

Dietrich

The last import was logged - and failed because of a timeout error:

  Import failed:
  Traceback (most recent call last):
  Failure: twisted.internet.error.TimeoutError: User timeout caused connection failure.

(from http://launchpadlibrarian.net/19558491/blender-trunk-log.txt )

So there are still chances that the import works one of the next times :)

The last imports worked - so cscvs worked just fine :)

Thank you!

By the way, wouldn't it make sense to set the development focus to the new import?

Yep, done. I've also marked the old import as abandoned. It's wierd that the new import only has 145 revisions versus the thousands of revisions in the old one, no?

Thanks :)

> It's wierd that the new import only has 145 revisions versus the thousands of revisions in the old one, no?

Yes. It would have been much nicer to fix the import problem of the old branch.

But people who are interested in the revisions of the blender main development line can always access them using the official blender repository.

The important thing is that launchpad makes it much much easier to work on patches or customisations of the main blender code which are not (yet) of any obvious interest for the average blender user seen from the perspective of the core blender developers and therefore would never have a chance to enter the blender repository.

Until now I used my private blender SVN repository and imported the blender sources as a "vendor drop" (see paragraph "Vendor Branches" in chapter 4. "Branching and Merging" of the "Version Control with Subversion" book,
http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html ). Of course, this also meant to loose blenders revision history and made updating difficult and time consuming. But even if so, this approach is of course much much better than working without any version control at all...

Blenders development model favours one general solution for everybody at the place of different branches for different user profiles. For this reason only a relatively small group of selected people with much time to devote to the blender development are allowed to write to the blender SVN repository and of course only if the core developers agree that the patch is of a general interest. Worse, patches which do not look interesting to the main developers are "rejected" from the patch tracker so that they do not have any chance to develop to something more interesting. this is especially frustrating for people who rely on these patches. Bazaar looks like the ideal "fix" for this kind of elitist development model (...which, by the way, seems to be the same as for the main part of launchpad itself?!? :).

Some time ago there was an experimental blender tree (tuhopuu = evil tree) where people where allowed to open their own branch to play around with the blender sources. But for some reason it seems to have been abandoned.

Anyway. Thanks for your help :)

Dietrich

...reading my last comment once again, I have to confess that I am not very happy about it: It sounds way too negative concerning the blender team and not as what I intended to say - sorry!

Of course those people I am criticising are the same who developed blender - and I am most grateful to them :)

Maybe, for a project as small as blender, their development model is the only one which leaves the development team with some time to work on blenders sources themselves beside managing, revising and integrating patches.

Probably I should say: I am grateful to subversion for helping the main developers to concentrate on their goal - and to bazaar to still give me a chance to work on my own customisation also :)

So here a revised version: Thank you, Ton & group for developing Blender! And another "Thank you" to the launchpad team for making it easy to work on private versions :)

Dietrich