Typically, the glsas contain a full package atom, but glsa-201612-40.xml does not. <package name="squashfs-tools" auto="yes" arch="*"> Please change to sys-fs/squashfs-tools <package name="sys-fs/squashfs-tools" auto="yes" arch="*"> Now, emerge -v @security fails with two exceptions portage.exception.InvalidAtom: squashfs-tools portage.glsa.GlsaFormatException: invalid package name: squashfs-tools This breaks the complete @security mechanism, even when squashfs-tools is not installed. Probably, it would be best to only ignore wrong definitions bit still process valid GLSAs? Cheers, Jan Reproducible: Always
Fixed.
(In reply to Aaron Bauman from comment #1) > Fixed. Great! Thanks & keep up the good work! Jan