Released on 7/15/06. Even the ChangeLog page looks cool: http://www.blender.org/cms/Changes_since_last_ver.727.0.html Thanks.
Hrm ... there's an ebuild in Portage, but it's tr
Hrm ... there's an ebuild in Portage, but it's très b0rken. It wants to download blender-2.42.tar.bz2, and there is no such file on download.blender.org/source ... only .tar.gz for 2.42.
The directory structure of the blender-2.42.tar.gz has also changed and no longer has a "blender" folder in it. It is now called "blender2.42" The error I get when I try to compile is below. This can me fixed by changing the $S directory in the ebuild to match new structure. Calculating dependencies... done! >>> Emerging (1 of 1) media-gfx/blender-2.42 to / >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking blender-2.42.tar.gz ;-) >>> Unpacking source... >>> Unpacking blender-2.42.tar.gz to /var/tmp/portage/blender-2.42/work cp: cannot stat `/var/tmp/portage/blender-2.42/work/blender/source/blender/blenpluginapi': No such file or directory /usr/portage/media-gfx/blender/blender-2.42.ebuild: line 65: cd: /var/tmp/portage/blender-2.42/work/blender: No such file or directory * Applying blender-2.37-dirs.patch ... * Failed Patch: blender-2.37-dirs.patch ! * ( /usr/portage/media-gfx/blender/files/blender-2.37-dirs.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/blender-2.42/temp/blender-2.37-dirs.patch-7739.out !!! ERROR: media-gfx/blender-2.42 failed. Call stack: ebuild.sh, line 1539: Called dyn_unpack ebuild.sh, line 711: Called src_unpack blender-2.42.ebuild, line 66: Called epatch '/usr/portage/media-gfx/blender/files/blender-2.37-dirs.patch' eutils.eclass, line 333: Called die !!! Failed Patch: blender-2.37-dirs.patch! !!! If you need support, post the topmost build error, and the call stack if relevant.
That's okay - even if you change the ebuild to successfully download - it buggers out on the blender-2.37-dirs.patch: >>> Unpacking blender-2.42.tar.gz to /var/tmp/portage/blender-2.42/work cp: cannot stat `/var/tmp/portage/blender-2.42/work/blender/source/blender/blenp luginapi': No such file or directory /usr/portage/media-gfx/blender/blender-2.42.ebuild: line 65: cd: /var/tmp/portag e/blender-2.42/work/blender: No such file or directory * Applying blender-2.37-dirs.patch ... * Failed Patch: blender-2.37-dirs.patch ! * ( /usr/portage/media-gfx/blender/files/blender-2.37-dirs.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/blender-2.42/temp/blender-2.37-dirs.patch-12406.out !!! ERROR: media-gfx/blender-2.42 failed. Call stack: ebuild.sh, line 1545: Called dyn_unpack ebuild.sh, line 711: Called src_unpack blender-2.42.ebuild, line 66: Called epatch '/usr/portage/media-gfx/blender/ files/blender-2.37-dirs.patch' eutils.eclass, line 333: Called die !!! Failed Patch: blender-2.37-dirs.patch! !!! If you need support, post the topmost build error, and the call stack if rel evant. Here's where the build takes place: /var/tmp/portage/blender-2.42/work/blender2.42/source/blender/src/ - so a 2.42 needs to be added to the diff call for it to work if indeed that patch is still needed. Can basic things like this be tested *before* the ebuild is sent down to portage?
Yep - aside from changing tar.bz2 to tar.gz, I changed S=${WORKDIR}/${PN} to S=${WORKDIR}/blender2.42 Changing to ${P} wouldn't work - because that made it look for blender-2.42 rather than blender2.42. They just had to change the basic directory structure...
Created attachment 91853 [details, diff] Patch to the ebuild in portage Here, just made a patch to the ebuild that addresses the above issues: -Switched from tar.bz2 to tar.gz -Replaced "S=${WORKDIR}/${PN}" with "S=${WORKDIR}/${PN}${PV}" to match blender's change in naming convention in a way that should work in future versions so long as their naming convention is the same as this release.
... fixed ...
*** Bug 140636 has been marked as a duplicate of this bug. ***
