| 1 |
On 12/16/20 11:34 AM, Miles Malone wrote: |
| 2 |
> What's happening when you do emerge -avuDN --with-bdeps=y |
| 3 |
> --backtrack=100 @world ? Giving portage the flexibility to solve it |
| 4 |
> with some extra backtracking and increasing the scope to world might |
| 5 |
> fix it, if not then we can revisit it? |
| 6 |
|
| 7 |
|
| 8 |
I don't remember if I've tried that combination, I'll do so now. |
| 9 |
|
| 10 |
|
| 11 |
... you include -a. Under what situation might I respond to the prompt |
| 12 |
with 'no'? |
| 13 |
|
| 14 |
|
| 15 |
|
| 16 |
> |
| 17 |
> On Wed, 16 Dec 2020 at 20:24, n952162 <n952162@×××.de> wrote: |
| 18 |
>> 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). |
| 19 |
>> |
| 20 |
>> Is there a way to force the PYTHON_TARGETS of the dependency? |
| 21 |
>> |
| 22 |
>> Slot collision: |
| 23 |
>> |
| 24 |
>> dev-python/jinja:0 |
| 25 |
>> |
| 26 |
>> (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 |
| 27 |
>> 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)" |
| 28 |
>> |
| 29 |
>> |
| 30 |
>> dev-python/jinja (Argument) |
| 31 |
>> |
| 32 |
>> (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 |
| 33 |
>> 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" |
| 34 |
>> |
| 35 |
>> If the package was good enough before, it's likely still good enough. 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 dev-python/setuptools dev-python/setuptools_scm dev-python/certifi dev-python/markupsafe dev-python/jinja dev-libs/libxml2 |
| 49 |
>> |
| 50 |
>> |
Archives