Example: https://bugs.gentoo.org/882075 not presently shown on https://packages.gentoo.org/maintainer/java@gentoo.org/security or https://packages.gentoo.org/packages/dev-java/testng/security
Currently the bug per maintainer in p.g.o are associated based on the packages. So if this bug wasn't connected with the package, it won't associate with maintainer. Why wasn't it associated with the package? This is the weird part, since it starts with exactly the $PN.
(In reply to Arthur Zamarin from comment #1) > [...] > Why wasn't it associated with the package? This is the weird part, since it > starts with exactly the $PN. Is it a question of bug assignment? Security bugs are assigned to security@gentoo.org with package maintainer in CC.
I've pushed a fix [1] to staging area. Because of triggers, CI pipelines and such, I think in about ~5 hours it would deploy and update all the bugs [2]. If it works, I'll then push to main instance. In short, the issue was simple, missing category "Gentoo Security" in the search. [1] https://gitlab.gentoo.org/gentoo/soko/-/commit/d66d5a1763da2d507a79ce6a60b5014e017bed55 [2] https://packagestest.gentoo.org/maintainer/java@gentoo.org/security
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/sites/soko.git/commit/?id=cc293da8812e7cff7c12bc7c54707ecb9a68d141 commit cc293da8812e7cff7c12bc7c54707ecb9a68d141 Author: Arthur Zamarin <arthurzam@gentoo.org> AuthorDate: 2023-04-21 11:56:05 +0000 Commit: Arthur Zamarin <arthurzam@gentoo.org> CommitDate: 2023-04-21 12:22:28 +0000 updater/bugs: add missing "Gentoo Security" category for search Closes: https://bugs.gentoo.org/904703 Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org> pkg/portage/bugs/bugs.go | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-)