I'mm having this issues since..., well it was a long time, maybe after the r1 release that I masked every 2.7.3-r* package because otherwise I will get: % laditray «─┘ Traceback (most recent call last): File "/usr/bin/laditray", line 24, in <module> import laditools File "/usr/lib64/python2.7/site-packages/laditools/__init__.py", line 19, in <module> from jack_menu import manager, find_data_file File "/usr/lib64/python2.7/site-packages/laditools/jack_menu.py", line 24, in <module> from config import config File "/usr/lib64/python2.7/site-packages/laditools/config.py", line 19, in <module> from xml.dom.ext import PrettyPrint ImportError: No module named ext laditools comes from ladi-overlay, so no official support. But I'm opening, lastly this bug, because I took some time to examine '/usr/lib64/python2.7/site-packages/_xmlplus/dom/ext' or '/usr/lib64/python2.7/xml/dom' and there's no apparent filename change between 2.7.3 and 2.7.3-r2. The modules are there but laditray won't find the appropriate module in a case and find the modules in the other. Reproducible: Always Steps to Reproduce: 1.laditray 2. 3. Actual Results: File "/usr/lib64/python2.7/site-packages/laditools/config.py", line 19, in <module> from xml.dom.ext import PrettyPrint ImportError: No module named ext Expected Results: execute the script/program
You're right - no support. But: 1. IIRC, while not in that overlay, there's a more recent version of laditools available 2. for a hint how to *properly* fix this see dev-java/javatoolkit/files/javatoolkit-0.3.0-no-pyxml.patch
