Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 554438 - glsa-check fails on 201507-12 - 'Invalid Tag found: ', 'h1')
Summary: glsa-check fails on 201507-12 - 'Invalid Tag found: ', 'h1')
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: GLSA Errors (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Security
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-10 16:15 UTC by Tomáš Mózes
Modified: 2016-07-01 12:19 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomáš Mózes 2015-07-10 16:15:06 UTC 
On amd64 with:
app-portage/gentoolkit 0.3.0.9
sys-apps/portage 2.2.20

# glsa-check -v -t all
invalid GLSA: 201507-12 (error message was: ('Invalid Tag found: ', 'h1'))
Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.3/glsa-check", line 336, in <module>
    myglsa = Glsa(myid, glsaconfig)
  File "/usr/lib64/python3.3/site-packages/gentoolkit/glsa/__init__.py", line 505, in __init__
    self.read()
  File "/usr/lib64/python3.3/site-packages/gentoolkit/glsa/__init__.py", line 523, in read
    self.parse(urlopen(myurl))
  File "/usr/lib64/python3.3/site-packages/gentoolkit/glsa/__init__.py", line 537, in parse
    self.DOM = xml.dom.minidom.parse(myfile)
  File "/usr/lib64/python3.3/xml/dom/minidom.py", line 1960, in parse
    return expatbuilder.parse(file)
  File "/usr/lib64/python3.3/xml/dom/expatbuilder.py", line 914, in parse
    result = builder.parseFile(file)
  File "/usr/lib64/python3.3/xml/dom/expatbuilder.py", line 205, in parseFile
    parser.Parse(buffer, 0)
xml.parsers.expat.ExpatError: mismatched tag: line 73, column 12
Comment 1 Mikle Kolyada (RETIRED) archtester Gentoo Infrastructure gentoo-dev Security 2015-07-10 17:34:01 UTC 
the version field was empty. Should be fixed now in glsa git repo. Thanks!
Comment 2 Tomáš Mózes 2015-07-11 04:06:00 UTC 
Seems like some weird text got into h1:

  <resolution>
    <p>Gentoo discontinued support for libCapsiNetwork.
      We recommend that users unmerge it:
    </p>

    <h1 id="emerge---unmerge-net-libslibcapsinetwork">emerge --unmerge
      ▒~@~Xnet-libs/libcapsinetwork▒~@~Y
    </h1>
  </resolution>
Comment 3 Aaron Bauman (RETIRED) gentoo-dev 2016-07-01 07:44:38 UTC 
(In reply to Tomáš Mózes from comment #2)
> Seems like some weird text got into h1:
> 
>   <resolution>
>     <p>Gentoo discontinued support for libCapsiNetwork.
>       We recommend that users unmerge it:
>     </p>
> 
>     <h1 id="emerge---unmerge-net-libslibcapsinetwork">emerge --unmerge
>       ▒~@~Xnet-libs/libcapsinetwork▒~@~Y
>     </h1>
>   </resolution>

Is this issue still present for you?
Comment 4 Tomáš Mózes 2016-07-01 11:30:05 UTC 
(In reply to Aaron Bauman from comment #3)
> (In reply to Tomáš Mózes from comment #2)
> > Seems like some weird text got into h1:
> > 
> >   <resolution>
> >     <p>Gentoo discontinued support for libCapsiNetwork.
> >       We recommend that users unmerge it:
> >     </p>
> > 
> >     <h1 id="emerge---unmerge-net-libslibcapsinetwork">emerge --unmerge
> >       ▒~@~Xnet-libs/libcapsinetwork▒~@~Y
> >     </h1>
> >   </resolution>
> 
> Is this issue still present for you?

Nope, this got fixed a year ago ;)
Comment 5 Aaron Bauman (RETIRED) gentoo-dev 2016-07-01 12:19:41 UTC 
(In reply to Tomáš Mózes from comment #4)
> (In reply to Aaron Bauman from comment #3)
> > (In reply to Tomáš Mózes from comment #2)
> > > Seems like some weird text got into h1:
> > > 
> > >   <resolution>
> > >     <p>Gentoo discontinued support for libCapsiNetwork.
> > >       We recommend that users unmerge it:
> > >     </p>
> > > 
> > >     <h1 id="emerge---unmerge-net-libslibcapsinetwork">emerge --unmerge
> > >       ▒~@~Xnet-libs/libcapsinetwork▒~@~Y
> > >     </h1>
> > >   </resolution>
> > 
> > Is this issue still present for you?
> 
> Nope, this got fixed a year ago ;)

Awesome. I was reviewing the XML and could't replicate the issue.  Thank you for the report.