Dependency Conflict Output is Hard to Read

[danielsdeleo]

When hab gets a dep conflict, it prints the full dep graph, which can be quite large for something like a ruby app. An example of that is here: https://gist.github.com/danielsdeleo/c431943a6f6244a68fabbb70be4fef07 It's 255 lines long and shows me a lot of unrelated information. In order to understand where the dependencies are coming from, the relevant info is just this:

kallistec/chef-dk/2.3.9/20171004215509
    core/ruby/2.4.2/20170914220737
        core/openssl/1.0.2j/20170513215106 (*)
    core/openssl/1.0.2j/20170926165227 (*)

It also could just be written in english saying something like:

Your plan has a dependency on core/openssl which is resolved to core/openssl/1.0.2j/20170926165227 but core/ruby which is included by your plan was was built with core/openssl/1.0.2j/20170513215106

It would be great also to provide some advice on how best to resolve the situation, when feasible.

[reset]

@danielsdeleo absolutely, I particularly think the english/human readable version is the way to go

[eeyun]

Yes indeed. Can't agree enough.

[rickmarry]

totally agree.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale[bot]]

This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details.