Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#37285 - [blender] build revision unkown

Attached to Project: Community Packages
Opened by gandalf3 (gandalf3) - Friday, 11 October 2013, 02:32 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 23 October 2013, 01:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Running 'blender --version' returns

Blender 2.68 (sub 0)
build date: 2013-08-04
build time: 13:07:48
build revision: unknown
build platform: Linux
build type: Release
...
(the important part being 'build revision: unknown')

This is not only annoying because the blender package is sometimes built from SVN, (not an official release) and it is then hard to tell what revision of blender one is using. (useful knowledge for e.g. bug reports.) But it also breaks some user made python scripts, e.g. this one here: https://github.com/zeffii/GL-fillet/


Steps to reproduce:

Run 'blender --version' or 'blender -v'
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Wednesday, 23 October 2013, 01:56 GMT
Reason for closing:  Won't fix
Additional comments about closing:  I won't try to hack the rev into the build system but if you give me a patch I will gladly integrate it.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 17 October 2013, 15:39 GMT
User made scripts are buggy if they don't handle "unknown" which is a perfectly valid default value. Furthermore, it is not set for builds that do not contain a .svn directory (as per blender's cmake file). I could set it in cases where I build from svn, but then I also provide the svn rev in the pkgver. All in all, I don't really see the need to bother. Also, I don't see a way to get the revision from official releases (not svn).

Are you willing to provide a patch? If you only need the rev for debugging purposes, check pkgver.
Comment by gandalf3 (gandalf3) - Sunday, 20 October 2013, 01:33 GMT
$pkgver is good enough for me, though I might try and work out how to set it as it would be nice to keep scripts that assume this will work working.

Loading...