hi, the glsa-200709-18.xml contains UTF-8 chars, which crashes glsa-check -l 'new' 200709-16 [U] Lighttpd: Buffer overflow ( www-servers/lighttpd ) 200709-17 [U] teTeX: Multiple buffer overflows ( app-text/tetex ) Traceback (most recent call last): File "/usr/bin/glsa-check", line 206, in ? sys.exit(summarylist(glsalist)) File "/usr/bin/glsa-check", line 172, in summarylist 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 470, in parse self.description = getText(myroot.getElementsByTagName("description")[0], format="xml") File "/usr/lib/gentoolkit/pym/glsa.py", line 233, in getText return str(rValue) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 544: ordinal not in range(128) Removing the char "é" in a name in description fixed it for me (/usr/portage/metadata/glsa/glsa-200709-18.xml line 40 : >/usr/sbin/sendmail (CVE-2007-4538), and Frédéric Buclin discovered bash: syntax error near unexpected token `CVE-2007-4538') Reproducible: Always Steps to Reproduce: 1.emerge --sync 2.glsa-check -l 'new' 3.
We *really* should get Bug 162493 fixed.
(In reply to comment #1) > We *really* should get Bug 162493 fixed. > Yeah :/ for the moment I just fixed this glsa.