Gentoo Archives: gentoo-user

From: Miles Malone <m.malone@××××××××××××××××××.net>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
Date: Wed, 16 Dec 2020 11:20:52
Message-Id: CAM8Dd_3OJ2f3vR9NNGMCnuBdZWh_ndoc7E09_hPp0-YEtTiHTA@mail.gmail.com
In Reply to: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision by n952162
1 If it's wanting to downgrade something you definitely wouldnt want
2 downgraded is one, but feel free to omit the "a" and do the above
3 anyway
4
5 On Wed, 16 Dec 2020 at 21:06, n952162 <n952162@×××.de> wrote:
6 >
7 > On 12/16/20 11:34 AM, Miles Malone wrote:
8 > > What's happening when you do emerge -avuDN --with-bdeps=y
9 > > --backtrack=100 @world ? Giving portage the flexibility to solve it
10 > > with some extra backtracking and increasing the scope to world might
11 > > fix it, if not then we can revisit it?
12 >
13 >
14 > I don't remember if I've tried that combination, I'll do so now.
15 >
16 >
17 > ... you include -a. Under what situation might I respond to the prompt
18 > with 'no'?
19 >
20 >
21 >
22 > >
23 > > On Wed, 16 Dec 2020 at 20:24, n952162 <n952162@×××.de> wrote:
24 > >> In an update with several slot collisions (see attachment), I'm zero-ing in on the simplest, where a package is to be replaced by the same package, but with different PYTHON_TARGETS (at least, that's how I interpret it).
25 > >>
26 > >> Is there a way to force the PYTHON_TARGETS of the dependency?
27 > >>
28 > >> Slot collision:
29 > >>
30 > >> dev-python/jinja:0
31 > >>
32 > >> (dev-python/jinja-2.11.2-r1:0/0::gentoo, ebuild scheduled for merge) USE="-doc -examples -test" ABI_X86="(64)" PYTHON_TARGETS="python3_8 python3_9 (-pypy3) -python3_6 -python3_7" pulled in by
33 > >> dev-python/jinja[python_targets_python3_9(-),python_single_target_python3_9(+)] required by (sys-auth/pambase-20201103:0/0::gentoo, ebuild scheduled for merge) USE="nullok passwdqc sha512 -caps -debug -elogind -gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -pwhistory -pwquality -securetty (-selinux) -systemd" ABI_X86="(64)"
34 > >>
35 > >>
36 > >> dev-python/jinja (Argument)
37 > >>
38 > >> (dev-python/jinja-2.11.2-r1:0/0::gentoo, installed) USE="-doc -examples -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python3_6 -python3_8 -python3_9" pulled in by
39 > >> dev-python/jinja[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, installed) USE="-doc -latex -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python3_6 -python3_8 -python3_9"
40 > >>
41 > >> If the package was good enough before, it's likely still good enough. Where's the problem? I've (unsuccessfully) made these attempts:
42 > >>
43 > >> # */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
44 > >> #*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
45 > >> # just have one set
46 > >> */* PYTHON_TARGETS: python3_8
47 > >>
48 > >> The sphinx ebuild has no targets, but does have this:
49 > >>
50 > >> PYTHON_COMPAT=( python3_{6..9} pypy3 )
51 > >>
52 > >> The emerge command was:
53 > >>
54 > >> sudo emerge --verbose=y -vuUD --verbose-conflicts dev-python/setuptools dev-python/setuptools_scm dev-python/certifi dev-python/markupsafe dev-python/jinja dev-libs/libxml2
55 > >>
56 > >>
57 >