which is used by some of the ~ubuntu-sru team members to find packages that are 'ready' to promote to -updates, so this one may have caused confusion as it was still showing this bug as yellow (i.e. not verified yet).
I think the ~ubuntu-sru team has tooling (probably from ubuntu-archive-tools project) that automatically updates all listed bugs with 'verification-RELEASE-needed' tags, it might be useful to include something like that into security tooling to add similar tags based on the changelog 'LP: #NNNNNN' bug tags.
Anyway, hopefully this can be released to -updates; we have another libseccomp patch we'd like to upload from bug 1861177.
I think having 2 bugs is fine, it's just that doing so for libseccomp (where it's applied to all sru releases) adds both bugs to the pending-srus page: /people. canonical. com/~ubuntu- archive/ pending- sru.html
https:/
which is used by some of the ~ubuntu-sru team members to find packages that are 'ready' to promote to -updates, so this one may have caused confusion as it was still showing this bug as yellow (i.e. not verified yet).
I think the ~ubuntu-sru team has tooling (probably from ubuntu- archive- tools project) that automatically updates all listed bugs with 'verification- RELEASE- needed' tags, it might be useful to include something like that into security tooling to add similar tags based on the changelog 'LP: #NNNNNN' bug tags.
Anyway, hopefully this can be released to -updates; we have another libseccomp patch we'd like to upload from bug 1861177.