After emerging layman it crash while attempting to sync the overlay list. After trying several things I ended-up at a python error : "No module named pyexpat" And in fact, emerging pyxml solved the problem. Reproducible: Always Steps to Reproduce: 1. Emerge layman-1.1.1 (without having pyxml on your system, and the ebuild will not ask for it) 2. Try to sync the overlay list (layman -S) 3. Layman crash Trying to sync Actual Results: layman is unusable and his overlay list empty Expected Results: Layman sync the overlay list and enable you to view/add overlays from the list I guess this problem would not exist is pyxml was a dependency of layman
(In reply to comment #0) > After emerging layman it crash while attempting to sync the overlay list. After > trying several things I ended-up at a python error : "No module named pyexpat" > And in fact, emerging pyxml solved the problem. > > Reproducible: Always > > Steps to Reproduce: > 1. Emerge layman-1.1.1 (without having pyxml on your system, and the ebuild > will not ask for it) > 2. Try to sync the overlay list (layman -L) > 3. Layman crash Trying to sync > > Actual Results: > layman is unusable and his overlay list empty > > Expected Results: > Layman sync the overlay list and enable you to view/add overlays from the list > > I guess this problem would not exist is pyxml was a dependency of layman >
Do you have dev-lang/python built with USE="xml"?
Yes, my python is emrged with the xml use dev-lang/python-2.5.2-r7 USE="berkdb gdbm ipv6 ncurses readline ssl threads xml -build -doc -examples -sqlite -tk -ucs2 -wininst" 0 kB Anyway, even if it was because of use of python, shouldn't the ebuild warn me as well (I already seen this for a gnome use required in a dep of a programme, so I guess it should ? )
Layman imports xml.dom.minidom from pyxml, right. Fixed in CVS now.
xml.dom.minidom is available also in dev-lang/python itself. $ python3.1 -c 'import xml.dom.minidom' $
