What steps will reproduce the problem?
1.Create packages 'x', 'a', and 'b' such that 'a' recommends 'b', and 'b' conflicts 'x'
2. Install 'x'
3. Try to install 'a'

What is the expected output? What do you see instead?
I expect 'a' to be installed, since 'b' is not an absolute dependency of 'a'.

Instead, nothing is installed.

What version of the product are you using? On what operating system?
0.3.0

Please provide any additional information below.
There are several other set-ups that cause related problems. For example if 'a' recommends 'b' and 'c', but 'c' conflicts with 'x', then only 'b' is installed and 'a' remains uninstalled. Note this is different from issue 162 since we do expect the non-conflicting packages to be installed in this case since recommends does not signal an absolute dependency. Similarly, if 'a' recommends 'b' and 'b' recommends 'c', but 'c' conflicts with 'x', then only 'b' is installed. I will create a test for this issue that covers each of these cases.

Originally reported by ericaustinyu, Jul 17, 2015
-----------------------------------------------------------------------------