Revision as of 08:09, 26 April 2010

AutoQA - add support for detecting false positives

Status

Contact

Mentor

Skills

IDEA

nobody

nobody

python, searching best solutions, working with big data-sets

Description

Generally this task would be about going through all the false positives AutoQA reported and figuring a method how not to run into the issue again and how to detect, if something changes. AutoQA needs to filter out this issues and not report them.

see the "libgnome" issue - somebody could add names of all packages and their's files into the dictionary

problem "doc-file-dependency /usr/share/doc/gnome-python2-gnomevfs-2.28.1/async-xfer.py /usr/bin/env" could be reported directly as a bug. Could some Python-guy confirm that "/usr/bin/env python" was obsoleted by "/usr/bin/python"?

migth ignore conflicts like this - like if I have conflicting basepackage-subpackage1-ver1 and basepackage-subpackage2-ver2 - I can determine, that the conflict is only theoretical, because if I have updated system, there will be only one of the packages.