We can use Beaker as a guinea pig for rpmdeplint, to validate our approach.
The outcome of this bug should be a working Jenkins job which will run for every new build of the beaker package in Brew, and will fail if there are any unsatisfied dependencies.
Beaker's target deployment platform is latest RHEL6 plus this repo of additional packages:
Another variation, which might be more or less difficult, would be to test against latest RHEL7 + EPEL7.
We are not targetting RHEL7 for deployment right now, but we want to in future, and so in preparation we have been building beaker packages for RHEL7. For our RHEL7 deployment we will be using EPEL7 rather than a "pile of random packages" repo maintained by us.
I'm not sure if it's possible to make the job fire on scratch builds -- normally you would want to ignore those, and not test them -- but if we can, it will give us a simple way to verify that the job actually works. We can just submit a scratch build of beaker with intentionally broken Requires hacked into the .spec.
If we are only triggering on eng-rhel-6-candidate tagged builds, that makes things a bit messier... we can still build intentionally broken packages into that tag (and then untag them after) but it leaves a permanent record in Brew, so it would leave a bit of a mess if we did lots of them.
Jon and I have been working on this.
Jenkins job definition: http://gerrit.beaker-project.org/4935
This is up and running now.