Since today glsa-check is failing. There other, similar bug reports, indicating that the media-libs/openjpeg GLSA XML document might contain invalid data Another reason might be, that I updated Python yesterday. /usr/bin/glsa-check -d affected Traceback (most recent call last): File "/usr/lib/python-exec/python3.7/glsa-check", line 139, in <module> if myglsa.isVulnerable(): File "/usr/lib/python3.7/site-packages/portage/glsa.py", line 650, in isVulnerable or (len(match(v, self.vardbapi)) > 0 \ File "/usr/lib/python3.7/site-packages/portage/glsa.py", line 296, in match return dbapi.match(atom) File "/usr/lib/python3.7/site-packages/portage/dbapi/vartree.py", line 567, in match origdep, mydb=self, use_cache=use_cache, settings=self.settings) File "/usr/lib/python3.7/site-packages/portage/dbapi/dep_expand.py", line 33, in dep_expand mydep = Atom(mydep, allow_repo=True) File "/usr/lib/python3.7/site-packages/portage/dep/__init__.py", line 1314, in __init__ raise InvalidAtom(self) portage.exception.InvalidAtom: <media-libs/openjpeg-*:1
If there’s other similar bug reports, please link them. Anyway, thanks for the report, please emerge —-sync as this was fixed last night. https://gitweb.gentoo.org/data/glsa.git/commit/?id=c62c6ad356b90a9c035e6ac2c40715c5fb63a836
