From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 386F51382C5 for ; Sat, 19 Dec 2020 12:35:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 659AFE08EB; Sat, 19 Dec 2020 12:35:00 +0000 (UTC) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2881CE088A for ; Sat, 19 Dec 2020 12:35:00 +0000 (UTC) Received: by mail-lf1-x133.google.com with SMTP id l11so12547321lfg.0 for ; Sat, 19 Dec 2020 04:34:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=V8Et5AhEDYQFlrU5l6vVRNjx82HsK843sZEFuhdSg/Y=; b=WGiJ1lz7zmpwUtYy5dFfTu/6iT1I+TvxBlDWCI8/+EEoVHFi2icAPvITsPyMpbt47I KPftubojvhQzwfDQfiLnucCepXJLOMIPYVGbAlJ1GjDTAbOuCvmhZznrNBr3/BIawaQK 3Pqhvt+Gg5YVEldUz78alMkYDy77Wp8oSEC82ksXfMcLzzkcwjWPkVtI/+J2QIWvJ5v0 WSzoqud4F2BVV878mrTiwWjHAJimjps2KQ6IKaijrbaHHwffvDIsbyCuF7+VzckDduwi JUfzrdYw0yY37YlmwjnhambRG+RgD3PhSJjHqXp6QEwdPFbYkZ99q8BUfDE/qYMaC8/d xDiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=V8Et5AhEDYQFlrU5l6vVRNjx82HsK843sZEFuhdSg/Y=; b=otlitOPCkVhVjZmDjpthtpYSQFM31MYAfwqjLq0NVlBBdssFD0v9Rf4VTE0w2wVbof ZWG+PI/u3o3j3loyeVfM143ofXWg3L1kYOCc7XRUOigdL87XQZDV/I+bpBIkemUP4HRV XqP741Qj4/rnzH74tVUxxjG/WJm1Vv3j80ZDh5xks8BNBA2o64l/zWQ7+zx8SHZumAtv cVEEkYC0OvLjz5DaBqU6+XDsF+La2LSA182mx6pgh502u4EKmzcfmdURNmLrZDFIU8uX X3ouv4IkQu6nq7U+Wl83DDLd7w1g+sGL7RZILxYrtOhypqrTXPNogTld6iuvpoIa+Trb vpHA== X-Gm-Message-State: AOAM530NgKRf2fsh0Pb3HVz7ab1gc0I8iOcCpQaFizorU6IOGG/dUk8H TJRk1q0YF4Huz2cDFBZBl5qx6I1o24TxMjwsYaSItqmlfUs= X-Google-Smtp-Source: ABdhPJxjG+edy6qKV3RIWiqc23EokHlGxUFjspN8tykb4zcPInOdlLCrCfstemCM7pha7kpsvyoLXWhUrAoH+cd0uLk= X-Received: by 2002:a19:c8cd:: with SMTP id y196mr3230887lff.400.1608381298348; Sat, 19 Dec 2020 04:34:58 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <361f9fda-9b2c-5e40-2b2e-28c35e52056b@web.de> <5dc17210-e2a7-eb9f-1d18-b1060572cdd6@web.de> In-Reply-To: <5dc17210-e2a7-eb9f-1d18-b1060572cdd6@web.de> From: Arve Barsnes Date: Sat, 19 Dec 2020 13:34:53 +0100 Message-ID: Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision To: Gentoo Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 167718b6-0879-46df-8914-5ad205aace43 X-Archives-Hash: d4d27b3e056c1136d8306867492c8de5 On Sat, 19 Dec 2020 at 12:11, n952162 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=3D"-test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"python3_8 (-pypy3) -python3_6 -python3_7 -python3_9" pulled in by >=3Ddev-python/setuptools-42.0.2[python_targets_pypy3(-)?,python_target= s_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,p= ython_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_t= arget_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=3D"-test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"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=3D"-test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"python2_7 python3_6 python3_7 (-pypy3) -python3_8 -python3_9" pulled in by >=3Ddev-python/setuptools-1.0[python_targets_python2_7(-),python_target= s_python3_6(-),python_targets_python3_7(-),-python_single_target_pypy3(-),-= python_single_target_python2_7(-),-python_single_target_python3_6(-),-pytho= n_single_target_python3_7(-),-python_single_target_python3_8(-),-python_sin= gle_target_python3_9(-)] required by (dev-python/cryptography-2.9:0/0::gentoo, installed) USE=3D"-idna -libressl -test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"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=3D"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=3D"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=3D"-idna -libressl -test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"python3_8 (-pypy3) -python3_6 -python3_7 -python3_9" pulled in by >=3Ddev-python/cryptography-1.3.4[python_targets_pypy3(-)?,python_targe= ts_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_targe= t_python3_8(-),-python_single_target_python3_9(-)] required by (dev-python/requests-2.24.0-r1:0/0::gentoo, ebuild scheduled for merge) USE=3D"ssl -socks5 -test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"python3_8 (-pypy3) -python3_6 -python3_7 -python3_9" ... and a few others ... (dev-python/cryptography-2.9:0/0::gentoo, installed) USE=3D"-idna -libressl -test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"python2_7 python3_6 python3_7 (-pypy3) -python3_8 -python3_9" pulled in by >=3Ddev-python/cryptography-2.8[python_targets_python2_7(-),python_targ= ets_python3_6(-),python_targets_python3_7(-),-python_single_target_pypy3(-)= ,-python_single_target_python2_7(-),-python_single_target_python3_6(-),-pyt= hon_single_target_python3_7(-),-python_single_target_python3_8(-),-python_s= ingle_target_python3_9(-)] required by (dev-python/pyopenssl-19.1.0:0/0::gentoo, installed) USE=3D"-doc -test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"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=3D"-doc -test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"python3_8 (-pypy3) -python3_6 -python3_7 -python3_9" pulled in by >=3Ddev-python/pyopenssl-0.14[python_targets_pypy3(-)?,python_targets_p= ython3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,pyth= on_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_targ= et_python3_6(-),-python_single_target_python3_7(-),-python_single_target_py= thon3_8(-),-python_single_target_python3_9(-)] required by (dev-python/urllib3-1.25.11:0/0::gentoo, ebuild scheduled for merge) USE=3D"-brotli -doc -test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"python3_8 (-pypy3) -python3_6 -python3_7 -python3_9" (dev-python/pyopenssl-19.1.0:0/0::gentoo, installed) USE=3D"-doc -test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"python2_7 python3_6 python3_7 (-pypy3) -python3_8 -python3_9" pulled in by >=3Ddev-python/pyopenssl-0.14[python_targets_python2_7(-),python_target= s_python3_6(-),python_targets_python3_7(-),-python_single_target_pypy3(-),-= python_single_target_python2_7(-),-python_single_target_python3_6(-),-pytho= n_single_target_python3_7(-),-python_single_target_python3_8(-),-python_sin= gle_target_python3_9(-)] required by (dev-python/urllib3-1.25.10:0/0::gentoo, installed) USE=3D"-brotli -doc -test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"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=3D"-brotli -doc -test" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"python3_8 (-pypy3) -python3_6 -python3_7 -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=3D"-doc -test" ABI_X86=3D"(64)" PYTHON_SINGLE_TARGET=3D"python3_6 -python2_7 -python3_5" PYTHON_TARGETS=3D"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=3D"gpg -test -tools" ABI_X86=3D"(64)" PYTHON_TARGETS=3D"python3_7 (-pypy3) -python3_6 -python3_8 -python3_9" Two packages are holding it back. net-misc/streamlink requires PYTHON_TARGETS=3D"python2_7 python3_6" and app-portage/gemato requires PYTHON_TARGETS=3D"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