Summary: | metabug: glsa-check / python-2.2 / pyxml problems | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Josh Glover (RETIRED) <jmglov> |
Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | guerrilla_thought, srcshelton |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Adds >=dev-python/pyxml-0.8.1 dependency |
Description
Josh Glover (RETIRED)
![]() Created attachment 29096 [details, diff]
Adds >=dev-python/pyxml-0.8.1 dependency
Any chance you could try to update python to 2.3 ? glsa-check should work just as fine without pyxml. I've seen one other report about strange things with glsa-check and python-2.2, so maybe the xml code has changed in subtle ways between 2.2 and 2.3. I unmerged PyXML, emerged dev-lang/python-2.3.3, ran /usr/sbin/python-updater, then unmerged Python 2.2. 'glsa-check -l' works properly. That just leaves us with the question of what exactly the dependencies of gentoolkit should be. well, I'm not so much worried about gentoolkit deps as about future portage deps as glsa-check will disappear in a few weeks and glsa.py will move to portage. *** Bug 48756 has been marked as a duplicate of this bug. *** *** Bug 48593 has been marked as a duplicate of this bug. *** added a check for python-2.3 in glsa.py and made gentoolkit-0.2.0_rc1 depending on that version, problems caused by pyxml are supposed to go away by remerging it. |