I emerged straw, and it won't start. Error message is this: Traceback (most recent call last): File "/usr/bin/straw", line 30, in ? import straw File "/usr/lib/python2.2/site-packages/straw/__init__.py", line 18, in ? from Config import Config, ConfigSaver File "/usr/lib/python2.2/site-packages/straw/Config.py", line 8, in ? import gconf ImportError: No module named gconf ------------------------------------ I think the module gconf for python comes with the gnome-python package, which I've remerged to no avail, any other ideas? Reproducible: Always Steps to Reproduce: 1. 2. 3.
it should come with gnome-python afaik yep.. i think after the configuration phase you can see which libs it is gonna build support for, check if it includes gconf. This should always go ok if you have a working gconf around.
Tried new version, straw 0.21.1, still won't find gconf module, I'm thinking that this is probably a gentoo problem, but I don't know any python so I can't look into it further.
try merging gnome-python with emerge gnome-python 2>&1 | tee /tmp/gnome-python.log and then attach the log
Created attachment 20786 [details] emerge log of gnome-python
well its looks like the module gets built, but theres some warnings and other stuff there. Those seem to be normal. Are you sure you have no old/self-installed/etc. material interfering with the modules, i actually think its a problem on your side and not gentoo in general (or we wouldve seen more of this). it might be as simple as a path problem, it seems like gconf is the first imported g* related dep. Do you have any other gnome-python 2 using apps.. can you make sure those work.
I'm pretty certain I did not do anything custom with gnome-python, or anything that would intefere. I'm not sure what other programs use gnome-python, if you give me one I'll be sure to try it.
none that i am aware of (directly at least). see if any of the packges come with test scripts in the source
Straw works fine now after I've moved up to python-2.3.
thats weird, it should work fine with both. I see no reason why it would build properly vs. 2.3 and not vs. 2.2. Makes me think more along the lines of a local path problem somewhere. closing (you couldve it when the problem got resolved)