Check all repositorites for package type #953
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When Ubuntu packages are updated because of security issues, it looks like their artifacts are published on both
-updates
and-security
repositories. (i.e. libssh)Currently, to mark a package as a
Security update
, only the first repo's name is checked (and it is usually the-updates
repo), so the package is not marked as a security update.If there are multiple repositories as origin for a package, this change loops all repos and not just the first one.
For some security packages,
package.candidate.origins
looks like this:Fixes #952