Summary: | dev-java/javatoolkit has unneeded dependency on dev-python/pyxml | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gian <news.gdc> |
Component: | [OLD] Java | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | arfrever |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gian
2008-09-01 18:25:19 UTC
The problem was in a bit different package, but thanks for reporting, now fixed in CVS :) Vlastimil: Care to point out what your idea is what the problem was? I'm inlined to think this is the same issue as I pointed out in bug 233166#c7 (In reply to comment #2) > Vlastimil: Care to point out what your idea is what the problem was? I'm > inlined to think this is the same issue as I pointed out in bug 233166#c7 The problem was not in dev-java/xml-commons-external specifically but in dev-java/javatoolkit which contains the python script /usr/bin/xml-rewrite-2.py which is called to rewrite build.xml of most Ant-based java packages such as the xml-commons-external. The fact that it has also 'xml' in name is not related, just coincidence that might be misleading :) As the xml-rewrite-2.py from javatoolkit rewrites build.xml files, it obviously has to parse them. Now I myself have no idea whether python should have xml support itself (the script uses xml.dom.minidom from what I can see), but since the 0.3.0 versions of javatoolkit have dev-python/pyxml dependency, I assumed it was really missing in 0.2.0 and added it. Now bug 233166 indicates that it's an error in python installation? The default XML parser implementing Python's xmlreader interface is pyexpat and part of Python, unless the - unsupported - "build" use flag is used or - unlikely - there's a bug in the Python build script. Another way to trigger this would be some non-Portage Python installation. Maybe folks having done the dead stupid libexpat.so.x -> y are affected, too.
These bug reports are most likely the symptom of locally screwed up systems as described above - but I cannot say for sure, if there isn't a real problem behind it.
From the Python documentation:
>It is important to note that modules in the xml package require that there be at least one SAX-compliant XML parser available. Starting with Python 2.3, the Expat parser is included with Python, so the xml.parsers.expat module will always be available. You may still want to be aware of the PyXML add-on package; that package provides an extended set of XML libraries for Python.
From what I see, you use stock Python and not any other libraries, which would require pyxml, so it is unneeded.
(In reply to comment #4) > These bug reports are most likely the symptom of locally screwed up systems as > described above - but I cannot say for sure, if there isn't a real problem > behind it. You were right, Carsten. As you suggested in 233166#c10 , /usr/lib/python2.5/lib-dynload/pyexpat.so was missing on my system and re-emergeing Python 2.5 fixed the problem. I think it happened during the upgrade from 2.4.3-r4 from stage3 to 2.5.2-r6. I remember some file collision, I probably did something wrong trying to fix that. Alright I'm renaming this bug as the original version of javatoolkit is gone but 0.3.0-r2 still has pyxml dependency which should therefore not be needed apparently? Fixed in dev-java/javatoolkit-0.3.0-r5. |