On Tue, 2010-03-09 at 15:28 -0500, Al Dunsmuir wrote:
> What Bill's talking about when he refers to 'autoqa
tests' are generic
> tests which are concerned with package quality, not really the software
> in the package: stuff like do the dependencies work, are there any clear
> errors in the file lists. They can be run on any RPM package, the
> software in the package doesn't really matter.
That makes sense.
How about things like rpmlint? Perhaps that would have caught the
bind/dnssec problems where user configs were directly rewritten
without backup to rpmnew files.
We have a tool called 'rpmguard' which is more or less a cousin of
rpmlint that looks at the differences between two versions of a package
and flags up critical changes. That's what will be implemented in AutoQA
and used at this 'test point'. See
https://fedorahosted.org/autoqa/wiki/rpmguard .
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net