glsa-check borked

Message

Shiner_Man · Post by **Shiner_Man** » Wed Apr 27, 2005 12:06 am

 glsa-check -l
WARNING: This tool is completely new and not very tested, so it should not be
used on production systems. It's mainly a test tool for the new GLSA release
and distribution system, it's functionality will later be merged into emerge
and equery.
Please read http://www.gentoo.org/proj/en/portage/glsa-integration.xml
before using this tool AND before reporting a bug.

[A] means this GLSA was already applied,
[U] means the system is not affected and
[N] indicates that the system might be affected.

Traceback (most recent call last):
  File "/usr/bin/glsa-check", line 155, in ?
    myglsa = Glsa(myid, glsaconfig)
  File "/usr/lib/gentoolkit/pym/glsa.py", line 414, in __init__
    self.read()
  File "/usr/lib/gentoolkit/pym/glsa.py", line 432, in read
    self.parse(urllib.urlopen(myurl))
  File "/usr/lib/gentoolkit/pym/glsa.py", line 446, in parse
    self.DOM = xml.dom.minidom.parse(myfile)
 File "/tmp/stage1root/usr/lib/python2.3/xml/dom/minidom.py", line 1918, in parse
  File "/tmp/stage1root/usr/lib/python2.3/xml/dom/expatbuilder.py", line 32, in ?
  File "/tmp/stage1root/usr/lib/python2.3/xml/parsers/expat.py", line 4, in ?
ImportError: No module named pyexpat

hmmm...pyexpat?

yaneurabeya · Post by **yaneurabeya** » Wed Apr 27, 2005 6:16 am

Either do emerge metadata and retry, or try reemerging python. Python's ebuild did state that there were some issues with older versions of python and older linked modules I believe...

Genone · Post by **Genone** » Wed Apr 27, 2005 9:34 am

if you have pyxml installed: remove it

Shiner_Man · Post by **Shiner_Man** » Wed Apr 27, 2005 10:33 am

re-emerging python did the trick. Thanks guys.