RFE: Search for packages that broke builds

[opoplawski]

swig 3.0.6 broke the plplot builds. I'd like to be able to search for what other packages broke with the swig update.

[opoplawski]

Now I'd like to know if the binutils 2.26-14.fc25 > 2.26-15.fc25 update broke anything else in addition to hdf5.

[msimacek]

How do you want the user interface to look like - what would be the input? I'm not sure how the UI should look like. Ideas for that:

• Make the dependency changes clickable link to list of same changes (it does exactly what you mentioned in the comment, but seems a bit limited)
• Have a form in which you enter both NVRs
• Have a list of updates for package, let you select from that
  For the actual search, there are multiple things to be considered:
• We cannot really tell whether the update broke the build. We only know that it broke and given package was updated. We need to make sure users clearly understand this
• We need to search for dependency changes within version range. Currently we use rpmlib for version comparisons, but for this we'll likely need to reimplement them in postgres
• When you ask for this information, it's likely that some builds weren't done yet. We should detect and display this somehow

[opoplawski]

I think the most useful/intuitive for me would be if each of the lines in the list of dependency changes, e.g.;

binutils 2.26-14.fc25 > 2.26-15.fc25

was a clickable link that got you a list of all builds (completed or scheduled as you mention) and their status that were built with that same exact dependency change. Perhaps with a subsequent list of builds whose previous NEVR was equal or less than the first and current was equal or greater than the second version.

The form version of entering a package and version(s) could be useful too

Right, this isn't a definitive source of blame, but a helpful tool.

Thanks for working on this, i think it would be quite helpful.

[msimacek]

The version with links to other affected package implemented in 1.9.0 and will be deployed soon