docker-compose and awscli have dependency conflict on ~amd64 during emerge @world: dev-python/colorama:0 (dev-python/colorama-0.3.3:0/0::gentoo, installed) pulled in by <=dev-python/colorama-0.3.3[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (dev-python/awscli-1.11.0:0/0::gentoo, installed) ^^ ^^^^^ (dev-python/colorama-0.3.7:0/0::gentoo, ebuild scheduled for merge) pulled in by >=dev-python/colorama-0.3.7[python_targets_python2_7(-)?,python_targets_python3_4(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-)] required by (app-emulation/docker-compose-1.10.0_pre20161220-r1:0/0::gentoo, ebuild scheduled for merge) ^^ ^^^^^ The simplest solution would be to bump awscli dependency on colorama.
awscli 1.11.28 is the first version allowing colorama up to version 0.3.7, 1.11.36 is the most current version.
Created attachment 459234 [details] ebuild for awscli 1.11.36 with updated colorama dependency please find attached an ebuild for the latest version of awscli with a version bump on colorama.
docker-compose-0.9 ebuild no longer exists, so it is not possible to merge both awscli and docker-compose in the same system. Are there any chances to include the ebuild by Ole in portage tree?
FYI: this also requires botocore update.
Created attachment 463590 [details] botocore-1.4.93.ebuild
Created attachment 463592 [details] awscli-1.11.47.ebuild
I can volunteer to maintain this package (I already do this in my overlay)
Created attachment 471898 [details] awscli 1.11.82 with updated colorama dependency
Moreover, v1.11.82 also depends on yaml so "dev-python/pyyaml" should be emerged too.