----- "Kamil Paral" kparal@redhat.com wrote:
As I have mentioned, it is currently possible for a package to "fly under our radar" by simply moving to official repositories (stable, updates, updates-testing) too soon. It caused by our current strategy to compare the package against its most recent version in official repositories.
Solution #2: Re-implement "search for latest" strategy I have been playing with koji command and it seems to be able to list all the history of builds with particular tag, not just the latest build. You can try it yourself: $ koji list-tag-history --package=PackageKit $ koji list-tagged dist-f12-updates PackageKit Therefore we can re-implement/add a new method to our library that would not just provide the latest build of a package, but all of them from the history. Then we would pick the one that suits us most. The API clearly offers this capabilities.
There is also one question that is directly connected to this topic. Which tags do we want to search through when looking for previous builds? c) Or the other way round, would it be better to search through only stable and -updates (skip -updates-testing)? When more builds are in testing repo, the differences would be displayed always against the latest build in stable repos (stable or -updates).
As mentioned in ticket #114 [1], I have implemented solution #2c). Only publicly available repos and searched through now bu default (can be changed) and searching for most recent package should work now correctly, you can specify maximum allowed EVR (exclusive).
No more fare dodgers! :)
autoqa-devel@lists.fedorahosted.org