A way other than a message string, that is. Something similar to the tuple returned by rpmts.check would be nice, in that it describes the type of the problem and the package (or packages) that triggered the problem. Maybe add properties to the exception types to provide more data?
Hi, DNF gets from depsolver library the same error strings you see in output. DNF doesn't take analyze these problems internally so there is no reason to parse them only because of exceptions. We will see if structured depsolving problems would help us with more readable error messages.
I'm not asking for more human-readable. I'm asking for more machine-readable, so that given a set of error conditions I can do something other than display a string, like maybe highlight something in a GUI.
*** This bug has been marked as a duplicate of bug 1059638 ***