If you are a Fedora packager, you might be interested to know that in
we replaced the depcheck
task. So if there are any dependency issues with the new update you submit
to Bodhi <https://bodhi.fedoraproject.org/>
;, you’ll see that as
*dist.rpmdeplint* failure (in the *Automated Tests* tab). The failure logs
should look very similar to the depcheck ones (basically, the logs contain
the errors dnf would spit out if it tried to install that package), so
there should be no transitioning effort needed.
If you listen for depcheck results somehow, i.e. in FMN
;, make sure to update your
rules to listen for *dist.rpmdeplint* instead. We have updated the default
filters in FMN, so if you haven’t changed them, you should receive
notifications for failures in rpmdeplint (and also upgradepath and
abicheck) for submitted updates owned by you.
The reason for this switch is that we wanted to get rid of custom
dependency checking (done directly on top of libsolv), and use an existing
tool for that instead. That saves us time, we don’t need to study all the
pitfalls of dependency resolution, and we benefit from someone else
maintaining and developing the tool (that doesn’t mean we won’t send
patches if needed). rpmdeplint <https://pagure.io/rpmdeplint>
exactly what we were looking for.
We will decommission depcheck task from Taskotron execution in the next few
days, if there are no issues. Rpmdeplint results are already being
published for all proposed updates.
If you have any questions, please ask in comments or reach us at #fedora-qa
freenode irc channel or
(You can view this announcement also at: https://kparal.wordpress.com/2