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 307BF1382C5 for ; Sat, 19 Dec 2020 11:12:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1419DE08F6; Sat, 19 Dec 2020 11:12:25 +0000 (UTC) Received: from 88.com (m32-140.88.com [43.250.32.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5A583E085B for ; Sat, 19 Dec 2020 11:12:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=88.com; s=dkim; h=To:From:Date; bh=qzf6MiWK2T0sUF5fCuazA3dFd/2KCuA2E6Gw3 04Zcxo=; b=Zsm40xAg84dgmN6Kv2TjWZYOF+SwGQ0i6ZrKOEQBhMWARzmzrUMlI LUDZ0DBkOfm2MueyEWyyVv93GVpsP1p6razpKFhbm40UAdW4se1zLU+DpZyRtM4r KrsHX1c4woKvUqRKv6Xxf56N3dkeJCKt1OBltj7keK56/nftzhAGMI= Received: from [172.24.1.53] (unknown [110.64.86.229]) by v_coremail-web-13 (Coremail) with SMTP id DSKnCgB3mhAH4N1fiw1eAA--.33692S3; Sat, 19 Dec 2020 19:12:09 +0800 (CST) To: gentoo-user@lists.gentoo.org References: <361f9fda-9b2c-5e40-2b2e-28c35e52056b@web.de> From: bobwxc Autocrypt: addr=bobwxc@88.com; keydata= xjMEX9dmjhYJKwYBBAHaRw8BAQdATS7zAfI+rxkgSbY4Jd8j7q6ebEExqNpzaSW7gN2n/xnN FmJvYnd4YyA8Ym9id3hjQDg4LmNvbT7CkQQTFggAORYhBPZFXHoI6KY3JMbVnjbpTqu1PlFr BQJf12aOBQkB4TOAAhsDBQsJCAcCBhUICQoLAgUWAgMBAAAKCRA26U6rtT5Ra2OOAPwIbFBA hEZC1G1tDItZT1YbmbGCH/lCcaU4yUtgtMkd6wEAppY/zQH61aqE+tn8LTFHlHi3u16vAS06 rLktsHo0+gbOOARf12aOEgorBgEEAZdVAQUBAQdAUAdCRe9meg+Uq23phb+QEz2ocpZvaU2a NjNl4LsZ90MDAQgHwn4EGBYIACYWIQT2RVx6COimNyTG1Z426U6rtT5RawUCX9dmjgUJAeEz gAIbDAAKCRA26U6rtT5Ra9T2AP45Txdf0LU/2sqx1KJAmaVzzx8XmHGzUznIRF15RPVq6gD/ dc7iWe3fYDG1zk96ogcXOYAkzBukmW9qxFhH26fVWQA= Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision Message-ID: <764b8e72-889d-40f5-5303-8d68716f399b@88.com> Date: Sat, 19 Dec 2020 19:12:06 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 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 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xXVnll9YeSMYUad3x5iSnDRWWXHvhD2ph" X-CM-TRANSID:DSKnCgB3mhAH4N1fiw1eAA--.33692S3 X-Coremail-Antispam: 1UD129KBjvJXoWxWFW3uF43Wry5CFy7Zw1fWFg_yoWrXFWUpF WxCF1jyF1ktr18A34xAr12gryrur47JFW7Gas8Kry8AF15Kay7XFWFvF4q9a13Xrs29F4Y yr43tw18ua9rZaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUvjb7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_tr0E3s1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr0_Cr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4 A2jsIEc7CjxVAFwI0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wASzI0EjI02j7Aq F2xKxwAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFV Cjc4AY6r1j6r4UM4x0Y48IcVAKI48JMx8GjcxK6IxK0xIIj40E5I8CrwCYjI0SjxkI62AI 1cAE67vIY487MxAIw28IcxkI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r4UMI8I3I0E5I 8CrVAFwI0_JrI_JrWlx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUJVWU XwCIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x 0267AKxVWUJVW8JwCI42IY6xAIw20EY4v20xvaj40_Jr0_JF4lIxAIcVC2z280aVAFwI0_ Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxUqW xRDUUUU X-Originating-IP: [110.64.86.229] X-CM-SenderInfo: pere45bf6ymhhfrp/ X-Archives-Salt: 8b06c824-bddb-4aa4-acee-75e6e348c326 X-Archives-Hash: 9bbd4049a7c8b6b79a0ceef8f5113439 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xXVnll9YeSMYUad3x5iSnDRWWXHvhD2ph Content-Type: multipart/mixed; boundary="KOLZvplkZMNDyVYSxZn6GXPITyQTUxnQw"; protected-headers="v1" From: bobwxc To: gentoo-user@lists.gentoo.org Message-ID: <764b8e72-889d-40f5-5303-8d68716f399b@88.com> Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision References: <361f9fda-9b2c-5e40-2b2e-28c35e52056b@web.de> In-Reply-To: --KOLZvplkZMNDyVYSxZn6GXPITyQTUxnQw Content-Type: multipart/mixed; boundary="------------4A6A3912083F6F5560C2CB79" Content-Language: en-US This is a multi-part message in MIME format. --------------4A6A3912083F6F5560C2CB79 Content-Type: multipart/alternative; boundary="------------7E5DBCB8BD53ACE3783A16E4" --------------7E5DBCB8BD53ACE3783A16E4 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable =E5=9C=A8 2020/12/19 =E4=B8=8B=E5=8D=886:20, n952162 =E5=86=99=E9=81=93: > On 12/16/20 11:59 AM, Arve Barsnes wrote: >> On Wed, 16 Dec 2020 at 11:34, Miles Malone >> wrote: >>> What's happening when you do emerge -avuDN --with-bdeps=3Dy >>> --backtrack=3D100 @world ? Giving portage the flexibility to solve i= t >>> with some extra backtracking and increasing the scope to world might >>> fix it, if not then we can revisit it? >> You should definitely try this first if you haven't. > > I have. > >>>> If the package was good enough before, it's likely still good enough= =2E Where's the problem? I've (unsuccessfully) made these attempts: >>>> >>>> # */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9 >>>> #*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9 >>>> # just have one set >>>> */* PYTHON_TARGETS: python3_8 >> Is there any reason that you need to add py3.9 to all packages? If you= >> need it for something special, add it to those packages only, and let >> portage take care of python targets for you instead of continuously >> trying these big hammers. Ideally you should have *no* python targets >> set manually in make.conf or USE files. > > I added it because I saw python3_9 in the PYTHON_TARGETS list for,=20 > e.g. jinja, and hoped that it would force compatibility. That is the=20 > question of the original post.=C2=A0 But that was just one of many atte= mpts. > >>>> The emerge command was: >>>> >>>> sudo emerge --verbose=3Dy -vuUD --verbose-conflicts dev-python/s= etuptools dev-python/setuptools_scm dev-python/certifi dev-python/markups= afe dev-python/jinja dev-libs/libxml2 >> Since it seems sphinx is installed with a different set of python >> targets than what you're trying to update, you should include sphinx >> in that emerge command to let it update to the same python targets and= >> solve the conflict. >> >> Regards, >> Arve > > I tried adding that but it didn't help. > > My latest command was: > > =C2=A0time emerge \ > =C2=A0=C2=A0=C2=A0 -v \ > =C2=A0=C2=A0=C2=A0 --deep \ > =C2=A0=C2=A0=C2=A0 --update \ > =C2=A0=C2=A0=C2=A0 --changed-use \ > =C2=A0=C2=A0=C2=A0 --verbose-conflicts \ > =C2=A0=C2=A0=C2=A0 --keep-going \ > =C2=A0=C2=A0=C2=A0 --with-bdeps=3Dy \ > =C2=A0=C2=A0=C2=A0 --changed-deps \ > =C2=A0=C2=A0=C2=A0 --backtrack=3D100 \ > =C2=A0=C2=A0=C2=A0 --newuse \ > dev-python/setuptools dev-python/setuptools_scm dev-python/certifi=20 > dev-python/markupsafe dev-python/jinja dev-libs/libxml2 dev-python/sphi= nx > > Below is the latest build output, with no PYTHON_TARGET specifications.= > =2E.. > > > real=C2=A0=C2=A0=C2=A0 0m45.063s > user=C2=A0=C2=A0=C2=A0 0m44.602s > sys=C2=A0=C2=A0=C2=A0 0m0.399s > > > I don't think this output or any list participant has actually=20 > identified where the problem here is.=C2=A0 In my original posting, the= =20 > only difference causing the slot collision for jinja was that one had=20 > a PYTHON_TARGETS of 3-7 and the other of 3-8.=C2=A0 I asked how to forc= e it=20 > to the correct value, but if someone explained that to me, I didn't=20 > understand it. > > > I'm afraid I'm going to have to give up on gentoo, although I'm pretty = > heavily invested in it.=C2=A0 I'm spending too many hours trying to=20 > maintain my systems and running into too many seemingly arbitrary=20 > roadblocks.=C2=A0 I'm told I should update every week, but I can't get = a=20 > system updated in a week. > > > /Is there=C2=A0 a fundamental goals issue here, when there's so much=20 > incompatibility between python3_{6,7,8,9}?=C2=A0 Do=C2=A0 packages real= ly need=20 > to care?=C2=A0 Are these versions so fundamentally different from each = > other, and programmers rely on those differences?=C2=A0 Or, is this=20 > somebody's orderliness tic?/ > So what do you really want to know? Using jinja with python3.6 3.7.3.8 3.9 at the same time? Or want to keep it with 3.6 or some else? The default PYTHON_TARGETS now change to 3_8 from 3_6. So when you=20 update, many software need to change. If you want to change that targets, just follow=20 https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS Maybe there no different or compatibility=C2=A0 with it actually, but we = need=20 a correct dependency. If you do not have enough time to update and config gentoo, =C2=A0maybe you should try other Linux like Arch(No need to compile) and= =20 Debian(less update). :-) --=20 bobwxc --------------7E5DBCB8BD53ACE3783A16E4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
=E5=9C=A8 2020/12/19 =E4=B8=8B=E5=8D=88= 6:20, n952162 =E5=86=99=E9=81=93:
On 12/16/20 11:59 AM, Arve Barsnes wrote:
On Wed, 16 Dec 2020 at 11:=
34, Miles Malone
<m.malone@homicidalteddybear.net>=
; wrote:

What's happening when yo=
u do emerge -avuDN --with-bdeps=3Dy
--backtrack=3D100 @world ?  Giving portage the flexibility to solve it
with some extra backtracking and increasing the scope to world might
fix it, if not then we can revisit it?

You should definitely try =
this first if you haven't.

I have. 

If the package was goo=
d enough before, it's likely still good enough.  Where's the problem?  I'=
ve (unsuccessfully) made these attempts:

# */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
#*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
# just have one set
*/* PYTHON_TARGETS: python3_8

Is there any reason that y=
ou need to add py3.9 to all packages? If you
need it for something special, add it to those packages only, and let
portage take care of python targets for you instead of continuously
trying these big hammers. Ideally you should have *no* python targets
set manually in make.conf or USE files.

I added it because I saw python3_9 in the PYTHON_TARGETS list for, e.g. jinja, and hoped that it would force compatibility.=C2=A0= That is the question of the original post.=C2=A0 But that was jus= t one of many attempts. 

The emerge command was=
:

sudo emerge --verbose=3Dy -vuUD   --verbose-conflicts   dev-python/setupt=
ools dev-python/setuptools_scm dev-python/certifi dev-python/markupsafe d=
ev-python/jinja dev-libs/libxml2

Since it seems sphinx is i=
nstalled with a different set of python
targets than what you're trying to update, you should include sphinx
in that emerge command to let it update to the same python targets and
solve the conflict.

Regards,
Arve

I tried adding that but it didn't help.

My latest command was:

=C2=A0time emerge \
=C2=A0=C2=A0=C2=A0 -v \
=C2=A0=C2=A0=C2=A0 --deep \
=C2=A0=C2=A0=C2=A0 --update \
=C2=A0=C2=A0=C2=A0 --changed-use \
=C2=A0=C2=A0=C2=A0 --verbose-conflicts \
=C2=A0=C2=A0=C2=A0 --keep-going \
=C2=A0=C2=A0=C2=A0 --with-bdeps=3Dy \
=C2=A0=C2=A0=C2=A0 --changed-deps \
=C2=A0=C2=A0=C2=A0 --backtrack=3D100 \
=C2=A0=C2=A0=C2=A0 --newuse \
dev-python/setuptools dev-python/setuptools_scm dev-python/certifi dev-python/markupsafe dev-python/jinja dev-libs/libxml2 dev-python/sphinx

Below is the latest build output, with no PYTHON_TARGET specifications.

...


real=C2=A0=C2=A0=C2=A0 0m45.063s
user=C2=A0=C2=A0=C2=A0 0m44.602s
sys=C2=A0=C2=A0=C2=A0 0m0.399s


I don't think this output or any list participant has actually identified where the problem here is.=C2=A0 In my original postin= g, the only difference causing the slot collision for jinja was that one had a PYTHON_TARGETS of 3-7 and the other of 3-8.=C2=A0 = I asked how to force it to the correct value, but if someone explained that to me, I didn't understand it.


I'm afraid I'm going to have to give up on gentoo, although I'm pretty heavily invested in it.=C2=A0 I'm spending too many hours trying to maintain my systems and running into too many seemingly arbitrary roadblocks.=C2=A0 I'm told I should update ev= ery week, but I can't get a system updated in a week.


Is there=C2=A0 a fundamental goals issue here, when there's s= o much incompatibility between python3_{6,7,8,9}?=C2=A0 Do=C2=A0 = packages really need to care?=C2=A0 Are these versions so fundamentally different from each other, and programmers rely on those differences?=C2=A0 Or, is this somebody's orderliness tic?<= /p>

So what do you really want to know?
Using jinja with python3.6 3.7.3.8 3.9 at the same time?
Or want to keep it with 3.6 or some else?

The default PYTHON_TARGETS now change to 3_8 from 3_6. So when you update, many software need to change.
If you want to change that targets, just follow https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
Maybe there no different or compatibility=C2=A0 with it actually, but= we need a correct dependency.

If you do not have enough time to update and config gentoo,
=C2=A0maybe you should try other Linux like Arch(No need to compile) = and Debian(less update).
:-)
--=20
bobwxc
--------------7E5DBCB8BD53ACE3783A16E4-- --------------4A6A3912083F6F5560C2CB79 Content-Type: application/pgp-keys; name="OpenPGP_0x36E94EABB53E516B.asc" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="OpenPGP_0x36E94EABB53E516B.asc" -----BEGIN PGP PUBLIC KEY BLOCK----- xjMEX9dmjhYJKwYBBAHaRw8BAQdATS7zAfI+rxkgSbY4Jd8j7q6ebEExqNpzaSW7gN2n/xnNF= mJv Ynd4YyA8Ym9id3hjQDg4LmNvbT7CkQQTFggAORYhBPZFXHoI6KY3JMbVnjbpTqu1PlFrBQJf1= 2aO BQkB4TOAAhsDBQsJCAcCBhUICQoLAgUWAgMBAAAKCRA26U6rtT5Ra2OOAPwIbFBAhEZC1G1tD= ItZ T1YbmbGCH/lCcaU4yUtgtMkd6wEAppY/zQH61aqE+tn8LTFHlHi3u16vAS06rLktsHo0+gbOO= ARf 12aOEgorBgEEAZdVAQUBAQdAUAdCRe9meg+Uq23phb+QEz2ocpZvaU2aNjNl4LsZ90MDAQgHw= n4E GBYIACYWIQT2RVx6COimNyTG1Z426U6rtT5RawUCX9dmjgUJAeEzgAIbDAAKCRA26U6rtT5Ra= 9T2 AP45Txdf0LU/2sqx1KJAmaVzzx8XmHGzUznIRF15RPVq6gD/dc7iWe3fYDG1zk96ogcXOYAkz= Buk mW9qxFhH26fVWQA=3D =3D7iXM -----END PGP PUBLIC KEY BLOCK----- --------------4A6A3912083F6F5560C2CB79-- --KOLZvplkZMNDyVYSxZn6GXPITyQTUxnQw-- --xXVnll9YeSMYUad3x5iSnDRWWXHvhD2ph Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wnsEABYIACMWIQT2RVx6COimNyTG1Z426U6rtT5RawUCX93gBgUDAAAAAAAKCRA26U6rtT5Ra7cG AP4kzggawJE1qHcK5dJYRmWBaV27Wl17hFBk03k0zaSMbgEA6Csdgzoo0EvSg01FWltA8UDMLwui 7evKjddmDYmd2AA= =0gEI -----END PGP SIGNATURE----- --xXVnll9YeSMYUad3x5iSnDRWWXHvhD2ph--