GNOME Bugzilla – Bug 707998
orca can't find its modules after recent python dir changes
Last modified: 2013-09-12 22:30:21 UTC
I'm trying to run Orca under jhbuild and getting a traceback when orca tries to load its modules. Looks like a fallout from commit 38ee6dcf7ce6b20260c6498b31d31e74d7246680 that moved Orca's python modules from lib64 to lib. $ jhbuild run orca Traceback (most recent call last):
+ Trace 232477
from orca import debug
... and the orca executable has: pyexecdir = '${exec_prefix}/lib64/python3.3/site-packages'.replace('${exec_prefix}', '/media/build/gnome') The modules however are not installed in lib64/python3.3, but lib/python3.3.
Created attachment 254823 [details] [review] Update orca executable for the recent python dir changes ... so that orca finds its modules after commit 38ee6dcf7ce6b20260c6498b31d31e74d7246680
Review of attachment 254823 [details] [review]: And orca can be jhbuilt without weird python foo in the .jhbuildrc. Setting to accepted-commit_now, as "hell yeah!" ain't a status it seems. THANK YOU!!
Thanks! Attachment 254823 [details] pushed as f1ea839 - Update orca executable for the recent python dir changes