Conflicts while switching to python 3.14

[pizzuhh]

Hello
I have some questions and want to solve those conflicts.

Here's the emerge command I run: https://bpa.st/YOMA
I'm excluding syncplay as it doesn't have python 3.14 support yet (I think) and sys-cluster/ceph for the same reason.

I followed the news about how to update python versions (followed the "Safer upgrade procedure") and when I ran the 3rd emerge (PYTHON_TARGETS and PYTHON_SINGLE_TARGET set to only python3_14) I get all those conflicts. I'm not that experienced with gentoo and wish to understand what those conflicts really mean, I'm assuming that a dependency wants to upgrade to python3_14 only but the package depending on that dependency is built with python3_14 and python3_13 ?

[bstaletic]

I followed the news about how to update python versions (followed the "Safer upgrade procedure") and when I ran the 3rd emerge (PYTHON_TARGETS and PYTHON_SINGLE_TARGET set to only python3_14) I get all those conflicts.

You can't do that with ceph being held back. You have to satisfy ceph's dependencies - either keep those packages at python 3.13 or both python 3.13/3.14, or see if you can update the ebuild in your local overlay.
Also, syncplay isn't in the gentoo overlay as far as I can tell, so you should tell us how have you installed it.

[Hu]

syncplay is not in Gentoo now, but it once was. It was removed in media-video/syncplay: remove last-rited pkg. I hope OP is using a local overlay for this, and not still holding on to the ::gentoo build from April 2020 (or earlier).

[pizzuhh]

So ceph is causing all those conflicts? If you don't mind can you explain how you figured this out?

Also I got syncplay from guru overlay

[bstaletic]

So ceph is causing all those conflicts? If you don't mind can you explain how you figured this out?

Also I got syncplay from guru overlay

The conflict output is verbose and can be intimidating, but is pretty clear when you actually try to read it.
Here's an example:

Code: Select all

dev-python/flask:0

  (dev-python/flask-3.1.3:0/0::gentoo, ebuild scheduled for merge) USE="-doc -examples -test -verify-provenance" ABI_X86="(64)" PYTHON_TARGETS="python3_14 -python3_12 -python3_13" conflicts with
    dev-python/flask[python_targets_python3_13(-)] required by (sys-cluster/ceph-20.1.1-r1:0/0::gentoo, installed) USE="cephfs mgr parquet radosgw sqlite ssl (system-boost) systemd tcmalloc uring -babeltrace -custom-cflags -diskprediction (-dpdk) -fuse -grafana -jaeger -kafka -kerberos -ldap -lttng -nvmeof (-pmdk) -rabbitmq (-rbd-rwl) -rbd-ssd -rdma -rgw-lua (-selinux) -spdk -test -xfs -zbd" ABI_X86="(64)" CPU_FLAGS_X86="avx2 pclmul sse sse2 sse3 sse4_1 sse4_2 ssse3 -avx512f" LUA_SINGLE_TARGET="lua5-4 -lua5-3" PYTHON_TARGETS="python3_13 -python3_12"

The first line is the category/name:slot. In this case there's a problem with flask.
Then the line that starts with ( is what you attempted to build/install. You should check that it makes sense. In this case, you're attempting to build it with PYTHON_TARGETS="python3_14 -python3_12 -python3_13", which is expected.
Now for the fun part. Each indennted line explains a dependency which contradicts your "wishes" from the previous line. Specifically, something is requesting

Code: Select all

dev-python/flask[python_targets_python3_13(-)]

and that something is

Code: Select all

required by (sys-cluster/ceph

and I'm not going to read the rest of the line at all.

ceph does not directly cover all conflicts, but the direct conflicts get propagated, causing conflicts for ceph's dependencnies as well.
I don't like mentally resolving the dependency graph, so once ceph is conflicts are resolved, I can take another look at conflicts that remain, if any.

You could take a piece of paper and make a graph of conflicts:

• Start with ceph's direct conflicts
• Read ceph's python dependencies and look for them in the conflict list
• Recurse into dependencies' dependencies until an iteration that does not find anything in the conflict list.
• Once done, check which conflicts you have not touched yet.

It's easier to get ceph updated, or just stay on python 3.13 for a while longer.

EDIT: Regarding syncplay, it does not appear in the conflict list, so it's fine to --exclude it for now. Yes, it has python dependencies, but I bet that the three dependencies it pulls in are pulled in, on your system, only by syncplay.

EDIT2: Another brief look... pythran and some others are configured with python 3.13 and python 3.14, which also causes a bunch of conflicts.