On Sat, 19 Dec 2020 at 12:11, n952162 <n952...@web.de> wrote:
> In the original posting of this thread, I presented a slot collision
> where the only difference between the two packages was the
> PYTHON_TARGET. I interpret that to mean that new dependencies want the
> new python. Since the package is the same, it ought to be possible to
> tell emerge(1) to assume a specific PYTHON_TARGET. Otherwise, there's no
> way out of the dilemma. If setting the PYTHON_TARGET as I've done it is
> not effective, do you know another way?
Maybe we should go back to the slot collision you get now then, and
try to explain how to read it, so maybe you can avoid these kinds of
things in the future (you can probably avoid them just by getting
through this, as it's been years since we've had such troublesome
upgrades as the recent python upgrades).
In an e-mail today, the FIRST errors after portage tells you what
packages it wants to upgrade, you get this:
dev-python/setuptools:0
(dev-python/setuptools-50.3.0:0/0::gentoo, ebuild scheduled for
merge) USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_8 (-pypy3)
-python3_6 -python3_7 -python3_9" pulled in by
>=dev-python/setuptools-42.0.2[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/sphinxcontrib-devhelp-1.0.2:0/0::gentoo,
ebuild scheduled for merge) USE="-test" ABI_X86="(64)"
PYTHON_TARGETS="python3_8 (-pypy3) -python3_6 -python3_7 -python3_9"
... and many others that want to upgrade to the same ...
(dev-python/setuptools-46.4.0-r3:0/0::gentoo, installed) USE="-test"
ABI_X86="(64)" PYTHON_TARGETS="python2_7 python3_6 python3_7 (-pypy3)
-python3_8 -python3_9" pulled in by
>=dev-python/setuptools-1.0[python_targets_python2_7(-),python_targets_python3_6(-),python_targets_python3_7(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/cryptography-2.9:0/0::gentoo, installed)
USE="-idna -libressl -test" ABI_X86="(64)" PYTHON_TARGETS="python2_7
python3_6 python3_7 (-pypy3) -python3_8 -python3_9"
... and again others with the same problem ...
So, most packages want to upgrade to the latest version, with
PYTHON_TARGETS="python3_8". As far as I know, the top packages are
those that the system wants to automatically upgrade normally.
Then, the first package in the next list is
dev-python/cryptopgraphy-2.9.0, which requires setuptools-46.4.0-r3,
the last version which supports PYTHON_TARGETS="python2_7 python3_6
python3_7". If this was the latest version of cryptography, you might
be stuck here for a while, maybe waiting for an update for
cryptography, but it is not, a newer version is available. So why is
portage not able to upgrade it? It tells you further down:
dev-python/cryptography:0
(dev-python/cryptography-3.2.1:0/0::gentoo, ebuild scheduled for
merge) USE="-idna -libressl -test" ABI_X86="(64)"
PYTHON_TARGETS="python3_8 (-pypy3) -python3_6 -python3_7 -python3_9"
pulled in by
>=dev-python/cryptography-1.3.4[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/requests-2.24.0-r1:0/0::gentoo, ebuild
scheduled for merge) USE="ssl -socks5 -test" ABI_X86="(64)"
PYTHON_TARGETS="python3_8 (-pypy3) -python3_6 -python3_7 -python3_9"
... and a few others ...
(dev-python/cryptography-2.9:0/0::gentoo, installed) USE="-idna
-libressl -test" ABI_X86="(64)" PYTHON_TARGETS="python2_7 python3_6
python3_7 (-pypy3) -python3_8 -python3_9" pulled in by
>=dev-python/cryptography-2.8[python_targets_python2_7(-),python_targets_python3_6(-),python_targets_python3_7(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/pyopenssl-19.1.0:0/0::gentoo, installed)
USE="-doc -test" ABI_X86="(64)" PYTHON_TARGETS="python2_7 python3_6
python3_7 (-pypy3) -python3_8 -python3_9"
So here we have the same problem with dev-python/pyopenssl-19.1.0,
there is a newer version available, but portage can't upgrade it, so
we need to move on to the next step once more.
dev-python/pyopenssl:0
(dev-python/pyopenssl-19.1.0-r1:0/0::gentoo, ebuild scheduled for
merge) USE="-doc -test" ABI_X86="(64)" PYTHON_TARGETS="python3_8
(-pypy3) -python3_6 -python3_7 -python3_9" pulled in by
>=dev-python/pyopenssl-0.14[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/urllib3-1.25.11:0/0::gentoo, ebuild scheduled
for merge) USE="-brotli -doc -test" ABI_X86="(64)"
PYTHON_TARGETS="python3_8 (-pypy3) -python3_6 -python3_7 -python3_9"
(dev-python/pyopenssl-19.1.0:0/0::gentoo, installed) USE="-doc
-test" ABI_X86="(64)" PYTHON_TARGETS="python2_7 python3_6 python3_7
(-pypy3) -python3_8 -python3_9" pulled in by
>=dev-python/pyopenssl-0.14[python_targets_python2_7(-),python_targets_python3_6(-),python_targets_python3_7(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/urllib3-1.25.10:0/0::gentoo, installed)
USE="-brotli -doc -test" ABI_X86="(64)" PYTHON_TARGETS="python2_7
python3_6 python3_7 (-pypy3) -python3_8 -python3_9"
So here we have the same problem with dev-python/urllib3-1.25.10,
there is a newer version available, but portage can't upgrade it, so
we need to move on to the next step once more.
dev-python/urllib3:0
(dev-python/urllib3-1.25.11:0/0::gentoo, ebuild scheduled for merge)
USE="-brotli -doc -test" ABI_X86="(64)" PYTHON_TARGETS="python3_8
(-pypy3) -python3_6 -python3_7 -python3_9" pulled in by
<dev-python/urllib3-1.26[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/requests-2.24.0-r1:0/0::gentoo, ebuild
scheduled for merge) USE="ssl -socks5 -test" ABI_X86="(64)"
PYTHON_TARGETS="python3_8 (-pypy3) -python3_6 -python3_7 -python3_9"
(dev-python/urllib3-1.25.10:0/0::gentoo, installed) USE="-brotli
-doc -test" ABI_X86="(64)" PYTHON_TARGETS="python2_7 python3_6
python3_7 (-pypy3) -python3_8 -python3_9" pulled in by
<dev-python/urllib3-1.26[python_targets_python2_7(-),python_targets_python3_6(-),python_targets_python3_7(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/requests-2.24.0:0/0::gentoo, installed)
USE="ssl -socks5 -test" ABI_X86="(64)" PYTHON_TARGETS="python2_7
python3_6 python3_7 (-pypy3) -python3_8 -python3_9"
So here we have the same problem with dev-python/requests-2.24.0,
there is a newer version available, but portage can't upgrade it, so
we need to move on to the next step once more.
dev-python/requests:0
(dev-python/requests-2.24.0-r1:0/0::gentoo, ebuild scheduled for
merge) USE="ssl -socks5 -test" ABI_X86="(64)"
PYTHON_TARGETS="python3_8 (-pypy3) -python3_6 -python3_7 -python3_9"
pulled in by
dev-python/requests[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/sphinx-3.2.1:0/0::gentoo, ebuild scheduled for
merge) USE="-doc -latex -test" ABI_X86="(64)"
PYTHON_TARGETS="python3_8 (-pypy3) -python3_6 -python3_7 -python3_9"
(dev-python/requests-2.24.0:0/0::gentoo, installed) USE="ssl -socks5
-test" ABI_X86="(64)" PYTHON_TARGETS="python2_7 python3_6 python3_7
(-pypy3) -python3_8 -python3_9" pulled in by
>dev-python/requests-2.21.0[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python3_7(-),python_single_target_python3_6(+)]
required by (net-misc/streamlink-1.1.1:0/0::gentoo, installed)
USE="-doc -test" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_6
-python2_7 -python3_5" PYTHON_TARGETS="python2_7 python3_6 -python3_5"
dev-python/requests[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (app-portage/gemato-16.2:0/0::gentoo, installed) USE="gpg
-test -tools" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3)
-python3_6 -python3_8 -python3_9"
Two packages are holding it back.
net-misc/streamlink requires PYTHON_TARGETS="python2_7 python3_6" and
app-portage/gemato requires PYTHON_TARGETS="python3_7".
gemato is already at the latest version, but on the old python
targets, not sure if that means it's been set in
/etc/portage/package.use, but net-misc/streamlink is an old version.
All its versions seem to be unstable though, and I think you were
running a stable system? You might need to manually keyword a newer
version (in /etc/portage/package.accept_keywords) to be able to
upgrade, or uninstall if this is not a package you need.
Hope this can help you read the massive amount of output portage
throws at you in these situations.
Regards,
Arve
