|
|
| (11 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
|
| | '''[[AutoQA]] is now obsolete and replaced by [[Taskotron]].''' |
| {{draft}}
| |
| | |
| = What Is Depcheck? =
| |
| Depcheck was created to detect packages with broken dependencies. As the test matures, it will eventually be a part of the rel-eng process to keep these broken packages from being pushed to testing or stable repositories.
| |
| | |
| = How Does Depcheck Work? =
| |
| Describing exactly how depcheck functions is outside the scope of this page but the basic idea is to trick yum into thinking that all available packages are installed and attempt to install the package under test. If there are problems installing that package, depcheck assumes that those errors are dependency problems and fails the error-causing package.
| |
| | |
| For more detailed information on depcheck, there are several blog posts about its internals (<ref>http://qa-rockstar.livejournal.com/10187.html</ref> <ref>http://qa-rockstar.livejournal.com/10368.html</ref> <ref> http://qa-rockstar.livejournal.com/10507.html</ref> <ref>http://blogs.fedoraproject.org/wp/wwoods/2011/01/03/depcheck-tags-and-timing-2/ </ref>).
| |
| | |
| = Understanding Failures =
| |
| | |
| = Fixing Failures =
| |
| | |
| = Getting Help =
| |
| If you still don't understand why your update failed the test, if you think there's something wrong in our test or its documentation or if you have any other suggestions, please [[AutoQA#Communicate|contact us]].
| |
| | |
| = Additional Information =
| |
| <references/>
| |
| | |
| | |
| [[Category:AutoQA tests]] | |
Latest revision as of 08:27, 22 June 2017
