| 1 |
在 2020/12/16 下午6:24, n952162 写道: |
| 2 |
> |
| 3 |
> In an update with several slot collisions (see attachment), I'm |
| 4 |
> zero-ing in on the simplest, where a package is to be replaced by the |
| 5 |
> same package, but with different PYTHON_TARGETS (at least, that's how |
| 6 |
> I interpret it). |
| 7 |
> |
| 8 |
> Is there a way to force the PYTHON_TARGETS of the dependency? |
| 9 |
> |
| 10 |
> Slot collision: |
| 11 |
> |
| 12 |
> dev-python/jinja:0 |
| 13 |
> |
| 14 |
> (dev-python/jinja-2.11.2-r1:0/0::gentoo, ebuild scheduled for merge) |
| 15 |
> USE="-doc -examples -test" ABI_X86="(64)" PYTHON_TARGETS="*python3_8 |
| 16 |
> python3_9 (-pypy3) -python3_6 -python3_7*" pulled in by |
| 17 |
> dev-python/jinja[python_targets_python3_9(-),python_single_target_python3_9(+)] |
| 18 |
> required by (sys-auth/pambase-20201103:0/0::gentoo, ebuild scheduled |
| 19 |
> for merge) USE="nullok passwdqc sha512 -caps -debug -elogind |
| 20 |
> -gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -pwhistory |
| 21 |
> -pwquality -securetty (-selinux) -systemd" ABI_X86="(64)" |
| 22 |
> |
| 23 |
> |
| 24 |
> dev-python/jinja (Argument) |
| 25 |
> |
| 26 |
> (dev-python/jinja-2.11.2-r1:0/0::gentoo, installed) USE="-doc |
| 27 |
> -examples -test" ABI_X86="(64)" PYTHON_TARGETS="*python3_7 (-pypy3) |
| 28 |
> -python3_6 -python3_8 -python3_9*" pulled in by |
| 29 |
> 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(-)] |
| 30 |
> required by (dev-python/sphinx-3.2.1:0/0::gentoo, installed) USE="-doc |
| 31 |
> -latex -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) |
| 32 |
> -python3_6 -python3_8 -python3_9" |
| 33 |
> |
| 34 |
> If the package was good enough before, it's likely still good enough. |
| 35 |
> Where's the problem? I've (unsuccessfully) made these attempts: |
| 36 |
> |
| 37 |
> # */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9 |
| 38 |
> #*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9 |
| 39 |
> # just have one set |
| 40 |
> */* PYTHON_TARGETS: python3_8 |
| 41 |
> |
| 42 |
> The sphinx ebuild has no targets, but does have this: |
| 43 |
> |
| 44 |
> PYTHON_COMPAT=( python3_{6..9} pypy3 ) |
| 45 |
> |
| 46 |
> The emerge command was: |
| 47 |
> |
| 48 |
> sudo emerge --verbose=y -vuUD --verbose-conflicts |
| 49 |
> dev-python/setuptools dev-python/setuptools_scm dev-python/certifi |
| 50 |
> dev-python/markupsafe dev-python/jinja dev-libs/libxml2 |
| 51 |
> |
| 52 |
> |
| 53 |
According to the |
| 54 |
https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS and your log |
| 55 |
|
| 56 |
may be set like |
| 57 |
|
| 58 |
# Replacing the profile default with specific implementation |
| 59 |
dev-python/* PYTHON_SINGLE_TARGET: python3_6 |
| 60 |
|
| 61 |
That will let all the dev-python target set to python3_6 |
| 62 |
|
| 63 |
-- |
| 64 |
bobwxc |
Archives