From Fedora Project Wiki

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Warning.png
This will be rewritten
This test case will be completely rewritten once the 'depcheck' script is finished. Potential_conflict.py won't be used for conflicts checking, the depcheck will be used instead.


Description

A test that ensures that there are no file or package conflicts in the repository being tested.

Setup

The host machine must have potential_conflicts.py script available. That script can be downloaded from AutoQA source code.

How to test

Use potential_conflict.py to test chosen repository for conflicts. If the repository has some parent repository (it contains just an updates for instance), don't forget to specify the parent repository too.

  1. Example 1 (testing 'fedora' repo for Fedora 12 for x86_64):
    ./potential_conflict.py --newest --tempcache --arch x86_64 --repoid fedora-x86_64 --repofrompath=fedora-x86_64,http://download.fedoraproject.org/pub/fedora/linux/releases/12/Everything/x86_64/os
  2. Example 2 (testing 'fedora-updates' repo for Fedora 12 for i386):
    ./potential_conflict.py --newest --tempcache --arch i386 --repoid fedora-updates-i386 --repofrompath=fedora-updates-i386,http://download.fedoraproject.org/pub/fedora/linux/updates/12/i386 --repoid fedora-i386 --repofrompath=fedora-i386,http://download.fedoraproject.org/pub/fedora/linux/releases/12/Everything/i386/os

Expected Results

  1. The output reports no package nor file conflicts.