Ticket #229 (closed enhancement: wontfix)
Create per-update file conflicts test
|Reported by:||jlaska||Owned by:|
|Priority:||major||Milestone:||Future test cases|
The conflicts test (appropriately named potential_conflicts.py) uses yum file lists to make an educated guess as to what file conflicts may be present. Also, this script operates over the entire repository, not just proposed updates. Note, that when installing packages directly on a system, yum relies on rpm logic to determine whether the transaction would result in file conflicts.
Similar in behavior to the depcheck test, we need a new test that takes the following inputs:
1) Proposed package update(s) 2) Desired repo (e.g. dist-f14-updates-testing)
Based on those inputs, the script would determine whether file conflicts would be introduced by the proposed package update(s). The script would return a list of package updates that could be successfully added to the requested repo without introducing file conflicts.