mirrorselect-2.2.2 wants ssl-fetch-0.2 to be installed, thus preventing ssl-fetch-0.3 to be merged > dev-python/ssl-fetch:0 > > (dev-python/ssl-fetch-0.3:0/0::gentoo, ebuild scheduled for merge) pulled in by > =dev-python/ssl-fetch-0.3 (Argument) > (dev-python/ssl-fetch-0.2:0/0::gentoo, installed) pulled in by > <dev-python/ssl-fetch-0.3[python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-)] required by (app-portage/mirrorselect-2.2.2:0/0::gentoo, installed) mirrorselect-2.2.2-r2, clears this issue so it may be good to stabilize as ssl-fetch-0.3 is now stable. Reproducible: Always
Yes, mirrorselect-2.2.2 was bumped to -r2 which included 2 patches, 1 of which modified the mirrorselect sources to be compatible with the api change that was needed in ssl-fetch. Now that ssl-fetch is stable, mirrorselect-2.2.2-r2 can be stablizized.
