public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: bobwxc <bobwxc@88.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
Date: Wed, 16 Dec 2020 18:56:03 +0800	[thread overview]
Message-ID: <7889aeb2-0fed-2fd2-8aa0-2fb051852edf@88.com> (raw)
In-Reply-To: <361f9fda-9b2c-5e40-2b2e-28c35e52056b@web.de>


[-- Attachment #1.1: Type: text/plain, Size: 2681 bytes --]

在 2020/12/16 下午6:24, n952162 写道:
>
> 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).
>
> Is there a way to force the PYTHON_TARGETS of the dependency?
>
> Slot collision:
>
> dev-python/jinja:0
>
>   (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
> 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)"
>
>
>     dev-python/jinja (Argument)
>
>   (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
> 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"
>
> If the package was good 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
>
> The sphinx ebuild has no targets, but does have this:
>
> PYTHON_COMPAT=( python3_{6..9} pypy3 )
>
> The emerge command was:
>
> 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
>
>
According to the 
https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS and your log

may be set like

# Replacing the profile default with specific implementation
dev-python/* PYTHON_SINGLE_TARGET: python3_6

That will let all the dev-python target set to python3_6

-- 
bobwxc



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

      parent reply	other threads:[~2020-12-16 10:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 10:24 [gentoo-user] override PYTHON_TARGETS to avoid a slot collision n952162
2020-12-16 10:34 ` Miles Malone
2020-12-16 10:59   ` Arve Barsnes
2020-12-19 10:20     ` n952162
2020-12-19 10:45       ` William Kenworthy
2020-12-19 11:15         ` n952162
2020-12-19 10:56       ` Arve Barsnes
2020-12-19 11:12         ` n952162
2020-12-19 11:35           ` Neil Bothwick
2020-12-19 14:19             ` n952162
2020-12-19 15:49               ` Neil Bothwick
2020-12-19 12:34           ` Arve Barsnes
2020-12-19 11:12       ` bobwxc
2020-12-19 11:33         ` n952162
2020-12-19 11:37           ` Neil Bothwick
2020-12-19 11:51             ` Michael
2020-12-19 12:02               ` Jude DaShiell
2020-12-19 11:35       ` Michael
2020-12-19 14:11         ` n952162
2020-12-19 15:54           ` Neil Bothwick
2020-12-19 16:13             ` Dale
2020-12-20 13:58       ` Róbert Čerňanský
2020-12-16 11:07   ` n952162
2020-12-16 11:20     ` Miles Malone
2020-12-16 11:22     ` Miles Malone
2020-12-16 12:25       ` Dale
2020-12-19  9:39   ` n952162
2020-12-16 10:56 ` bobwxc [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7889aeb2-0fed-2fd2-8aa0-2fb051852edf@88.com \
    --to=bobwxc@88.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox