After world update, I am said by enotice: Package: python-2.5.2-r7 * You have configured Python without XML support. * This is NOT a recommended configuration as you * may face problems parsing any XML documents. * You have configured Python without XML support. * This is NOT a recommended configuration as you * may face problems parsing any XML documents. * * If you have just upgraded from an older version of python you will * need to run: * * /usr/sbin/python-updater * * This will automatically rebuild all the python dependent modules * to run with python-2.5. * * Your original Python is still installed and can be accessed via * /usr/bin/python2.x. I ran it. Now I have this problem: dhp@moon-gen-3:~$ /usr/bin/Memo Traceback (most recent call last): File "/usr/lib/ROX-Lib2/python/rox/options.py", line 161, in __init__ doc = minidom.parse(path) File "/usr/lib/python2.5/xml/dom/minidom.py", line 1912, in parse from xml.dom import expatbuilder File "/usr/lib/python2.5/xml/dom/expatbuilder.py", line 32, in <module> from xml.parsers import expat File "/usr/lib/python2.5/xml/parsers/expat.py", line 4, in <module> from pyexpat import * ImportError: No module named pyexpat /usr/lib/rox/Memo/main.py:33: GtkDeprecationWarning: gtk.mainquit is deprecated, use gtk.main_quit instead g.mainquit() ClientCall object destroyed without waiting for response! Possible existing copy of Memo is not responding Traceback (most recent call last): File "/usr/lib/rox/Memo/memos.py", line 119, in __init__ doc = minidom.parse(path) File "/usr/lib/python2.5/xml/dom/minidom.py", line 1912, in parse from xml.dom import expatbuilder File "/usr/lib/python2.5/xml/dom/expatbuilder.py", line 32, in <module> from xml.parsers import expat File "/usr/lib/python2.5/xml/parsers/expat.py", line 4, in <module> from pyexpat import * ImportError: No module named pyexpat Traceback (most recent call last): File "/usr/lib/rox/Memo/AppRun", line 3, in <module> import main File "/usr/lib/rox/Memo/main.py", line 46, in <module> memo_list = memos.MasterList() File "/usr/lib/rox/Memo/memos.py", line 124, in __init__ root = doc.documentElement UnboundLocalError: local variable 'doc' referenced before assignment dhp@moon-gen-3:~$ I have yet to check if there can be a bad interaction with some stuff I have in my user dir (I also installed Memo and Rox in ~/ using 0install ) but as this short log does not mention /home at all, I think there is a bug at the distro level. python-updater *should* find that there is a problem. And does not. Rebuilding Memo says I have preserved libs (I am using stable with portage 2.2). After rebuild, the problem still exists. But those libs are only related with media-video/mjpegtools-1.9.0 and media-video/transcode-1.0.7 . Rebuilding these will not help. revdep-rebuild said everything is OK (normal since I am using portage 2.2). Memo was working yesterday. So the problem could be: - python-updater not finding the problem - Memo broken (rebuilding does not help) - interaction with my user datas (I will try Memo under an other user to check this) - portage 2.2 not being able to preserve required libs ? I will feedback in few hours.
Created attachment 182535 [details] /tmp/emerge--info [ebuild R ] sys-apps/portage-2.2_rc23 USE="doc -build -epydoc (-selinux)" LINGUAS="-pl" 0 kB [ebuild R ] dev-lang/python-2.5.2-r7 USE="berkdb doc examples gdbm ipv6 ncurses readline ssl threads -build -sqlite -tk -ucs2 -wininst -xml" 0 kB [ebuild R ] rox-extra/memo-2.0-r1 USE="libnotify" 0 kB [ebuild R ] app-admin/python-updater-0.5 0 kB
[ebuild R ] dev-libs/expat-2.0.1-r1 0 kB was installed, but python was compiled without XML. Please introduce a test and an eerror in Memo saying: if python compiled without XML => error "in order to use Memo please rebuild Pythont with XML flag ON". Problem fixed for me. Thanks bye.
Indeed. Though the python dep is in an eclass, and I suppose I'll have to figure out how to do perhaps to a multi-EAPI eclass.... But I digress. Thanks for the report, and I'll put that dep in once I figure out the best way.
Of course a dep would be the best way, but, in the worst case, at begin of Memo compile, just check with which FLAGS, python had been compiled (many ebuilds do this, and it's easy). It would not have prevent the problem, and the problem would not have been enlighted by "emerge -DaNuv world", but, it would have when I recompiled Memo. and this would have been nice.
and also python-2.6.1 doesn't have a xml use flag.
(In reply to comment #5) > and also python-2.6.1 doesn't have a xml use flag. ignore - i had an old version on python-2.6.1 installed.
Okay, memo-2.1 now depends on python[xml], and once it goes stable memo-2.0 will go away... And everyone will be happy ;)
