|
|
| Line 1: |
Line 1: |
| = What Is Depcheck? =
| | '''[[AutoQA]] is now obsolete and replaced by [[Taskotron]].''' |
| 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 prevent broken packages from being pushed to the ''testing'' or ''stable'' package 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 =
| |
| | |
| == Missing requirements ==
| |
| Looking at an [http://tflink.fedorapeople.org/autoqa/prettylog/depcheck_example_error.html example log], we see the following highlight:
| |
| <pre>
| |
| matahari-lib-0.4.1-2.fc14.i686 from pending has depsolving problems
| |
| --> Package: matahari-lib-0.4.1-2.fc14.i686 (pending)
| |
| --> Requires: libsigar.so
| |
| </pre>
| |
| | |
| In this case, {{package|matahari}} requires the shared library {{filename|libsigar.so}}. At the time the test ran, the shared library {{filename|libsigar.so}} was not provided by any available package.
| |
| | |
| == "Not Found" errors ==
| |
| Look at the following excerpt:
| |
| <pre>
| |
| SKIPBROKEN: --> Package: erlang-js-0.5.0-2.fc15.x86_64 (f15)
| |
| --> Requires: libjs.so.1()(64bit)
| |
| --> Removing: js-1.70-13.fc15.x86_64 (f15)
| |
| --> libjs.so.1()(64bit)
| |
| --> Updated By: 1:js-1.8.5-6.fc15.x86_64 (pending)
| |
| --> Not found
| |
| </pre>
| |
| | |
| Build {{filename|erlang-js-0.5.0-2.fc15.x86_64}} has broken dependencies. It requires <code>libjs.so.1()(64bit)</code> which is provided by {{filename|js-1.70-13.fc15.x86_64}}. But the {{package|js}} package is about to be updated (as part of this or some other update request) to {{filename|1:js-1.8.5-6.fc15.x86_64}}. And the latter build does not provide <code>libjs.so.1()(64bit)</code>, thus it is marked as '''Not found'''.
| |
| | |
| Let's confirm:
| |
| <pre>
| |
| $ repoquery -q --provides js-1.70-13.fc15.x86_64 | grep libjs
| |
| libjs = 1.70-13.fc15
| |
| libjs.so.1()(64bit)
| |
| $ repoquery -q --provides js-1.8.5-6.fc15.x86_64 | grep libjs
| |
| libjs = 1.8.5-6.fc15
| |
| </pre>
| |
| | |
| As you can see, by updating the {{package|js}} package the dependencies of {{package|erlang-js}} would be broken and that it the reason why depcheck rejected this update.
| |
| | |
| == Conflicts ==
| |
| | |
| Errors caused by packages conflicting each other should be ignored at the moment. The problem lies in the current implementation of depcheck, in which we 'bend' yum into believing that all the packages are installed at once, and then let it run its depsolver. This means, that if two (or more) packages conflict each other, then yum refuses to install them, and so they get rejected.
| |
| <pre>
| |
| SKIPBROKEN: 1:grub-0.97-77.fc16.x86_64 from pending has depsolving problems
| |
| SKIPBROKEN: --> grub conflicts with 1:grub2-1.99-2.fc16.x86_64
| |
| </pre>
| |
| | |
| = Fixing Failures =
| |
| Fortunately, the fixes for depcheck errors tend to be relatively straight-forward and tend to fall into one of two categories listed below.
| |
| | |
| <ol>
| |
| <li> '''Problems caused by your package'''<br/>
| |
| Examine any changes to <code>Provides</code>, <code>Requires</code> or <code>BuildRequires</code> in the {{filename|spec}} file. Ensure correct spelling of all dependencies and confirm that any changed requirements do resolve for the appropriate release. If the dependencies of your package have not changed, it's possible that other packages no longer satisfy the dependencies as expected. Read below for further guidance.
| |
| <br/>
| |
| The command {{command|repoquery}} is helpful to track dependencies.
| |
| | |
| <li> '''Problems caused by other package(s)'''<br/>
| |
| If your package failed because the dependencies of other packages changed (features they were providing changed or were removed), update the requirements of your package or consult with maintainers of the corresponding packages.
| |
| | |
| </ol>
| |
| | |
| = Other =
| |
| | |
| == Ignored builds ==
| |
| | |
| Sometimes, you'll encounter list of "ignored builds" in the report. First of all - do not be alarmed, it is not a wrong state (and we don't mark updates as FAILED if ignored builds occur). The ignored status usually means, that the update was probably changed, and more builds were added, and since we do some 'weird magic' with yum's database of installed packages, these are not recognized as updates, because these were tested in previous runs of Depcheck.
| |
| | |
| = 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]]
| |
