Bug 1183120

Summary:	RFE: provide a means of accessing the problems raised by resolve
Product:	[Fedora] Fedora	Reporter:	David Shea <dshea>
Component:	dnf	Assignee:	Honza Silhan <jsilhan>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	rawhide	CC:	akozumpl, jsilhan, mluscon, pablo.iranzo, packaging-team-maint, pnemade, rholy, tim.lauridsen
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-20 13:21:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1145250

Description David Shea 2015-01-16 18:09:18 UTC

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?

Comment 1 Honza Silhan 2015-01-20 12:13:48 UTC

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.

Comment 2 David Shea 2015-01-20 14:08:23 UTC

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.

Comment 3 Honza Silhan 2015-05-20 13:21:10 UTC


*** This bug has been marked as a duplicate of bug 1059638 ***