Bug 606140

Summary:	GLSA 201701-36: bad format of the XML, breaks glsa-check?
Product:	Gentoo Security	Reporter:	Kalin KOZHUHAROV <kalin>
Component:	Misc	Assignee:	Gentoo Security <security>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Kalin KOZHUHAROV 2017-01-18 02:24:35 UTC

This started a few days ago on several machines, one using python2.7, one using 3.4. It is probably caused by bad XML in GLSA 201701-36, since deleting this file manually stopped the error (found the offender by `strace -e open`).


Somewhat related to bug #599942 IMHO.

Reproducible: Always

Steps to Reproduce:
$ /usr/bin/glsa-check -q --verbose -l affected
Actual Results:  

Traceback (most recent call last):
  File "/usr/lib/python-exec/python2.7/glsa-check", line 181, in <module>
    myglsa = Glsa(x, glsaconfig)
  File "/usr/lib64/python2.7/site-packages/gentoolkit/glsa/__init__.py", line 505, in __init__
    self.read()
  File "/usr/lib64/python2.7/site-packages/gentoolkit/glsa/__init__.py", line 523, in read
    self.parse(urlopen(myurl))
  File "/usr/lib64/python2.7/site-packages/gentoolkit/glsa/__init__.py", line 570, in parse
    self.count = int(count)
AttributeError: Attr instance has no attribute '__trunc__'


Expected Results:  
201701-37 [N] [remote  ] libxml2: Multiple vulnerabilities ( dev-libs/libxml2-2.9.4 )

works fine (get expected results after:

$ mv /usr/portage/metadata/glsa/glsa-201701-36.xml /tmp

Comment 1 Mart Raudsepp gentoo-dev

2017-01-18 02:36:15 UTC

This couldn't have started happening before 14 hours ago from now, and was fixed 4 hours ago (+ sync propagation times). Though there was a period where a different GLSA was causing this.
Fixed per bug 606120, please sync

*** This bug has been marked as a duplicate of bug 606120 ***