Actions
Story #5740
closed
As a user, advisory collection names are unique within an advisory
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 78
Quarter:
Description
Background¶
As a part of #4295, two advisories can be merged into a new one which contains combined package list.
Motivation¶
Each package list consists of collections (usually 1 , but can be 0 or 2+ as well). Each collection has a name which is expected to be unique by dnf/yum client. If the name is not unique, only a subset of packages will be updated when advisory is applied on a user system.
Solution¶
Ensure the uniqueness of collection names at the time of combining two advisories into one.
If names are unique, preserve original names.
If names are the same, make them unique (e.g. append an ordinal number to the existing name)
Actions
.
Teach advisory-merge to avoid package-collection name collisions.
Closes a hole in a very specific edge case in advisory-merge during a copy operation. Requires two advisories that have:
Changes one sych collection's name to insure name-uniqueness.
Also, fixed a test_retention test to stop failing due to postgres non-determinism.
closes #5740 [nocoverage]