On 2/15/15 9:23 PM, David Steele wrote:
>> That seems a bit incredible, since port should be able to resolve the
>> dependencies by itself. I suggest that this should be reported as a bug
>> to MacPorts.
>
> Sure, that has been my experience, but the error message was very clear.
> Unfortunately I did not capture the error before I changed the order
> and the log file was removed on the next run.
How about uninstalling and reinstalling?
