starting with a clean amd64 stage3 when trying to emerge setuptools I get the following blocker. Seems to be a circular dependency: > 5af06c3fbb89 /usr/local/portage # emerge -av setuptools > > * IMPORTANT: 13 news items need reading for repository 'gentoo'. > * Use eselect news read to view new items. > > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild NS ] dev-lang/python-3.6.5:3.6/3.6m::gentoo [2.7.14-r1:2.7::gentoo, 3.5.5:3.5/3.5m::gentoo] USE="gdbm ipv6 ncurses readline ssl (threads) xml -build -examples -hardened -libressl -sqlite {-test} -tk -wininst" 16663 KiB > [ebuild R ] dev-python/setuptools-36.7.2::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_6* (-pypy) (-pypy3) -python3_4 -python3_5*" 710 KiB > [ebuild R ] dev-python/certifi-2018.4.16::gentoo PYTHON_TARGETS="python2_7 python3_6* (-pypy) (-pypy3) -python3_4 -python3_5* (-python3_7)" 147 KiB > > Total: 3 packages (1 in new slot, 2 reinstalls), Size of downloads: 17520 KiB > > !!! Multiple package instances within a single package slot have been pulled > !!! into the dependency graph, resulting in a slot conflict: > > dev-python/setuptools:0 > > (dev-python/setuptools-36.7.2:0/0::gentoo, ebuild scheduled for merge) pulled in by > dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/certifi-2018.4.16:0/0::gentoo, ebuild scheduled for merge) > > > dev-python/setuptools (Argument) > > (dev-python/setuptools-36.7.2:0/0::gentoo, installed) pulled in by > dev-python/setuptools[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (app-portage/gemato-13.0-r1:0/0::gentoo, installed) > > dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/certifi-2018.4.16:0/0::gentoo, installed) > > > > dev-python/certifi:0 > > (dev-python/certifi-2018.4.16:0/0::gentoo, ebuild scheduled for merge) pulled in by > >=dev-python/certifi-2016.9.26[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/setuptools-36.7.2:0/0::gentoo, ebuild scheduled for merge) > > > > (dev-python/certifi-2018.4.16:0/0::gentoo, installed) pulled in by > >=dev-python/certifi-2016.9.26[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/setuptools-36.7.2:0/0::gentoo, installed) >
Likely you are experiencing problems caused by the PYTHON_TARGETS profile change that was committed this week. Please try running an @world update, or at least rebuilding all installed python packages.
> Please try running an @world update, or at least rebuilding all installed python packages. I haven't finished doing this yet, but I'm running this in a Docker container using the stage3-amd64 image, which is derived directly from stage3.tar.gz This seems to hint at the stage3 not being up to date with the profile changes.
Yes, it is quite likely that a new stage3 tarball has not been built since the profile change was made. Give it a week or two and it will catch up.
I am having this problem as well, except with a Gentoo installation that is several years old. I have updated it on a (usually) daily basis. Update @world doesn't solve anything, just brings more packages into the conflict. In fact, it looks like no updates can be done without a massive masking of python packages. I expect trying that would result in an even bigger mess. The error messages are particularly opaque. Is it possible to back out the PYTHON_TARGETS change?
(In reply to rjgleits from comment #4) > Is it possible to back out the PYTHON_TARGETS change? Yes, you can put any PYTHON_TARGETS setting that you want in /etc/portage/make.conf, and it will override the profile setting. If you don't want to completely override the profile's PYTHON_TARGETS, you can use modify the USE variable to add/remove specific python_targets_* flags.
(In reply to Mike Gilbert from comment #3) > Yes, it is quite likely that a new stage3 tarball has not been built since > the profile change was made. Give it a week or two and it will catch up. This seems to be fixed, just ran the same test as before and it's working fine now. Seems like the stage3's have been updated.
