Project

Profile

Help

Story #5739

As a user, advisory version is considered at conflict resolution time

Added by ttereshc 25 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

Background

Currently advisory conflicts resolve according to #4295 which is based on updated timestamp and package list difference.

Motivation

Some advisories don't have updated timestamp but they bump advisory version in case of changes. (e.g. openSUSE ones). RH/Fedora advisories bump version as well but not for all changes, so it's not possible to switch to using version only for conflict resolution.

Solution

Version of advisory should be taken into consideration at conflict resolution time.
Updated timestamp has precedence.
When updated timestamp is absent or the same for both advisories, advisory versions should be compared.
The higher the version is, the newer the advisory.

Please register to edit this issue

Also available in: Atom PDF