When I had Cabal-1.12.0 in both my global and user databases, running virthualenv would fail.
Removing my user Cabal-1.12.0 fixed the problem, but was a dependency on the yesod I had built...
I don't know enough to say that having the same version of a package in my global and user databases isn't nonsensical, so maybe this is more an issue with me than with virthualenv -- and if so, then it might be beneficial (for clueless people like me :) to include a different error message.
Last bit of my virthualenv.log file (with the dependency strings) reformatted.
When I had Cabal-1.12.0 in both my global and user databases, running virthualenv would fail.
Removing my user Cabal-1.12.0 fixed the problem, but was a dependency on the yesod I had built...
I don't know enough to say that having the same version of a package in my global and user databases isn't nonsensical, so maybe this is more an issue with me than with virthualenv -- and if so, then it might be beneficial (for clueless people like me :) to include a different error message.
Last bit of my virthualenv.log file (with the dependency strings) reformatted.