Print latest *applicable* version of packages on conflicts

[bergmark]

Extension of #450, showing the latest isn't helpful when there is an upper bound, e.g.

--  Failure when adding dependencies:
      classy-prelude-conduit: needed (<0.12), latest is 0.12.0, but 0.12.0 found
      xml-conduit: needed (<1.3), latest is 1.3.0, but 1.3.0 found

Here it would be more useful to show the latest version of classy-prelude-conduit that's < 0.12. Perhaps change the message to say "latest applicable is ..."

[snoyberg]

Want to take a stab at this? May be faster than iterating together, and
this code is pretty well isolated.

On Fri, Jul 3, 2015, 11:24 AM Adam Bergmark notifications@github.com
wrote:

Extension of #450 #450,
showing the latest isn't helpful when there is an upper bound, e.g.

-- Failure when adding dependencies:
classy-prelude-conduit: needed (<0.12), latest is 0.12.0, but 0.12.0 found
xml-conduit: needed (<1.3), latest is 1.3.0, but 1.3.0 found

Here it would be more useful to show the latest version of
classy-prelude-conduit that's < 0.12. Perhaps change the message to say
"latest applicable is ..."

—
Reply to this email directly or view it on GitHub
#508.

[bergmark]

I might take a look over the weekend

[snoyberg]

Updating with awaiting-pr label

[snoyberg]

Bump