Package: scons Version: 0.98.2-1 Severity: serious Hi,
it started with my wondering whether I was hitting a regression in scons, which you can trigger by trying to build blender in a clean sid environment. AFAIUI by reading the diff, the Options->Variables transition is being initiated, being at the moment mostly transparent, then it's planned to warn for deprecation, and then to remove that compat layer completely. While I'm perfectly OK with the above plan, it looks like that compat layer just doesn't work. | scons: Reading SConscript files ... | ImportError: No module named BoolOption: | File "/home/kibi/hack/collab-maint/blender-2.45/SConstruct", line 44: | import tools.btools | File "/home/kibi/hack/collab-maint/blender-2.45/tools/btools.py", line 4: | import SCons.Options.BoolOption | make: *** [build-stamp] Error 2 You might not be able to reproduce it in a sid environment if you upgraded scons from a previous version (see my reopening #476976). Purging and reinstalling the scons package helps, or working in a clean sid chroot. I noticed that problem while preparing a security upload for Blender, that's why I'd like to avoid having to adapt it to the new Variable-way of doing things in scons, if possible. Mraw, KiBi.
signature.asc
Description: Digital signature
