| Summary: | sys-apps/portage: egencache --update-use-local-desc unhandled xml.etree.ElementTree.ParseError | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Zac Medico <zmedico> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
It's easy enough to trigger, for example an unexpected close tag raises this: xml.etree.ElementTree.ParseError: mismatched tag: line 4, column 4 |
Any code using xml.etree.ElementTree needs to handle xml.etree.ElementTree.ParseError: > Traceback (most recent call last): > File "/usr/lib/python-exec/python3.4/egencache", line 1119, in <module> > sys.exit(egencache_main(sys.argv[1:])) > File "/usr/lib/python-exec/python3.4/egencache", line 1067, in egencache_main > gen_desc.run() > File "/usr/lib/python-exec/python3.4/egencache", line 602, in run > target=_MetadataTreeBuilder())) > File "/usr/lib64/python3.4/xml/etree/ElementTree.py", line 1186, in parse > tree.parse(source, parser) > File "/usr/lib64/python3.4/xml/etree/ElementTree.py", line 604, in parse > parser.feed(data) > xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 13, column 18