Bug#570053: ITA: blender -- Very fast and versatile 3D modeller/renderer
Hi Rafael and Cyril,
Rafael Cunha de Almeida wrote, On 17/05/2010 07:38:
> Hello Cyril,
>
> I'm CCing this e-mail to you just to ask, when you say
>
> Enable the "security patch" again.
>
> what patch are you talking about? I looked at unstable's patches directory for
> the word security, but I didn't find anything. Is that some debian terminology
> I'm not familiar with?
AFAIK, I think it's the patch 02_tmp_in_HOME in 2.49+dfsg-2 branch. It
change the way blender save quit.blend into /tmp by saving it in
~/.blender/ . If it's this one, there is an upstream patch to review at
<http://projects.blender.org/tracker/?func=detail&atid=127&aid=22339&group_id=9>
.
> On Fri, May 14, 2010 at 12:56:42PM +0200, Kevin Roy wrote:
>> Rafael Cunha de Almeida wrote, On 14/05/2010 03:45:
>>>
>>> Cool, I think I can use some help :-). I'm not sure how to add two maintainers
>>> to a project, but we can figure it out later.
>>>
>>
>> Actually I'm completely new about the Debian packaging "world" and I am
>> still learning how it works. So I can work and contribute on the git and
>> let you the uploads thing.
>>
>
> Hello Kevin,
>
> Alright, I have been maintaining a patch, but I'm no expert either. Do you have
> jabber (it works on google talk as well)? Maybe you could add me:
> rca@jabber-br.org. That way we have faster communication.
>
Yes I'm using my google account to jabber a lot and I've just added you ;)
>>
>> Here is my github clone : git://github.com/kiniou/blender-debian.git
>> I forgot to tell I'm working/developping with Ubuntu Lucid actually but
>> i'm looking to build with pbuilder and Debian mirror. This is why i've
>> got a branch called ubuntu-lucid.
>
> I think that if you are chrooting to a debian tree it shouldn't matter if you
> use ubuntu or debian. My name on github is aflag: github.com/aflag. Can you add
> me to that project so we can both make changes to that repository?
I've added you as well.
> I have changed minor things on top of your modifications. I added a changelog
> entry and I've created the file debian/source/format. You need to add yourself
> to the changelog as well, take a look on dch to know how to add new entries on
> that file. I think a dch -a will work once you have your email and name
> configurated correctly.
>
> For now, my modifications are at:
> http://kontesti.me/~rafael/debian/blender/blender.git
> if you want to check out.
>
I'm checking it out :) . BTW I've created a launchpad PPA at
https://launchpad.net/~kiniou/+archive/ppa .
>> Strange ... the build failed for me at the linking process because of
>> openjpeg missing header. It failed only with pbuilder but not with
>> dpkg-buildpackage and so far I did not find any clue about this issue.
>
> That is strange. I haven't been using pbuilder, but I use debuild directly. I'm
> not sure why it wouldn't work with pbuilder. I'm not sure what that openjpeg
> library does, but if it adds feature to blender, it's nice to leave it on.
The libopenjpeg is used in the imbuf module which handles Texture
formats in blender. I just add -lopenjpeg in the root CMakeLists.txt and
pbuilder finally complete the build.
> BTW,
> why did you add
>
> OPTION(WITH_BUILDINFO "Include extra build details" ON)
> OPTION(WITH_INSTALL "Install accompanying scripts and language files needed to run blender" ON)
> I don't think there was new scripts added to it with WITH_INSTALL option.
Those options are ON by default on my svn checkout.
The WITH_INSTALL option is needed to install all python scripts and
locales in /usr/share/blender/2.5/ (cf. source/creator/CMakeLists.txt
+108) but i don't know if it's the right place for install.
The WITH_BUILDINFO just add build information like date, svn revision
... (cf. source/creator/CMakeLists.txt +90) so it's safe to leave it ON.
> I have been talking to people on IRC and it seems that blender
> internationalization isn't really ready yet. It seems like English is really the
> only option available. There's this guy named bdiego who seems to work with
> that. Perhaps he can give us some pointers as to how internationalization will
> work. However, I think we could just drop it altogether for now
> (/usr/share/blender/2.5/locale isn't even the right place for that to be, it
> should be at /usr/share/locale.)
This seems not to be a big priority upstream, but it may be trivial to
fix this and send a patch to them. I'll take a look at it.
> I think we should figure out our TODO list so we can divide the work to be done
> between us. The original TODO:
>
> - Enable the "security patch" again.
> => asking KiBi about it.
I can check if the upstream patch works.
> - Maybe double-check localization.
> => seems like there's no localization for now. Ask bdiego about it.
> - Check building within unstable.
> - Finally move 2.50 alpha 0 to unstable.
2.6 will be the "stabilised" version of blender according to upstream
roadmap <http://www.blender.org/development/release-logs/blender-250/>.
It may be better to stick with 2.5 in experimental and package 2.6 in
unstable when it will be released (normally around mid 2010).
>
> Next step I think is checking each of the current bugs to see if
> upstream mentions fixing them and also check if we can reproduce the bugs. Then
> we can update changelog as needed.
>
Yep, I totally agree with this and I've already looked in the bug
tracker .. there are some old bugs that can be closed but I've looked
too quickly to do a list :) .
>>> Collada seems to be needed in order to export blender projects to a XML format.
>>> It's possible to compile blender without it, but I think it would be much better
>>> to support it. Unfortunately I don't see collada (or opencollada) in debian's
>>> repository. Do you know anything about this issue?
>>
>> I remember that Collada export was done with some python script in 2.49
>> and I think it could be ported to 2.5 but maybe it's worth packaging
>> opencollada. Anyway for now I disabled it in the patch
>> 10_build_configuration for tests.
>
> Yes, I talked to KiBi on IRC and I think we're better off leaving that support
> out for now. It'd utimately require opencollada package to be created and
> maintained on debian. That's a thing to be thought about in the future, I think.
Ok with that too.
---
Kevin Roy
http://blog.knokorpo.fr
Reply to: