Hi All,

I was analyzing a problematic situation with ovirt-web-ui build breaking
OST for a day or two. It turned out the problem was about RPM versions
not being fine enough. The project used only the date part in their RPM
names, so the builds were named like this:

  1.8.2-0.20220607.git703b8f7.fc35
  1.8.2-0.20220607.git26ac92c.fc35
  1.8.2-0.20220607.gitf519b50.fc35

The problem with this approach is that among these versions the one with
the "biggest SHA" is considered to be the latest one, which is not
always true. The solution in this case would be to use finer RPM
versions that include at least the hour and the minute of the build
(although I can see most projects use seconds too). I posted [1] to fix
this in ovirt-web-ui,

but I can see other projects suffer from this
problem too (i.e. java-ovirt-engine-sdk4, ovirt-engine-ui-extensions)

[2]. Please make sure that you use RPM versions that are fine-enough.

Thanks, Marcin

[1] https://github.com/oVirt/ovirt-web-ui/pull/1599
[2]
https://copr.fedorainfracloud.org/coprs/ovirt/ovirt-master-snapshot/builds/