Can't see in any bug reports, but the latest GLSA emails from gentoo-announce contain Python tracebacks and errors embedded in the text. For example in GLSA 202305-19, instead of a list of affected packages it says: Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/glsamaker/models/glsa.py", line 326, in generate_mail_table return self._generate_mail_table() File "/usr/local/lib/python3.9/site-packages/glsamaker/models/glsa.py", line 297, in _generate_mail_table vuln.range_types_rev[vuln.pkg_range], vuln.version KeyError: None
Sorry, I thought I'd fixed all of these. I'll go over and fix the remaining ones later. I also note that I left a TODO in libapreq2 which I'll fix later today as well.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/data/glsa.git/commit/?id=732f6cefb4a1e4884e3fa3048d18faa0babd014a commit 732f6cefb4a1e4884e3fa3048d18faa0babd014a Author: Sam James <sam@gentoo.org> AuthorDate: 2023-05-04 07:06:24 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-05-04 07:06:24 +0000 [ GLSA 202305-20 ] Fix description Bug: https://bugs.gentoo.org/905652 Bug: https://bugs.gentoo.org/866536 Signed-off-by: Sam James <sam@gentoo.org> glsa-202305-20.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
I just need to finish resending the emails now.
Once the emails are done, I'll file a bug for improving the Portage handling of this as well.
OK, done. I'll file a separate bug for the Portage handling.
