| View previous topic :: View next topic |
| Author |
Message |
eklebanow
Tux's lil' helper
Joined: 08 Sep 2019
Posts: 116
|
 Posted: Mon Apr 21, 2025 6:25 pm Post subject: problems completing python3_13 upgrade |
 |
|
I followed instructions from the news feed to do the safer python upgrade procedure.
It did not go well.
I was finally able to get past a portage block but I have a bunch of updates/rebuilds which are being skipped due to a dependency conflict.
Can someone please help me out......
Here is what I get upon update command:
https://bpa.st/UZUQ |
|
| Back to top |
|
 |
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 2118
|
| Posted: Mon Apr 21, 2025 6:58 pm Post subject: |
|
|
| Code: | (dev-python/setuptools-78.1.0:0/0::gentoo, ebuild scheduled for merge) USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_11 python3_13 (-pypy3) (-pypy3_11) -python3_10 -python3_12 (-python3_13t)" conflicts with
>=dev-python/setuptools-78.1.0[python_targets_python3_11(-),python_targets_python3_12(-)] required by (dev-python/i3ipc-2.2.1-r1:0/0::guru, installed) USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_11 python3_12" |
This is your problem: dev-python:i3ipc::guru is not python 3.13 ready (at least as the ebuild is written)
Either i3ipc needs to be updated or else setuptools and other dependencies need to have both 3.12 and 3.13 enabled at the same time until it is. |
|
| Back to top |
|
|
eklebanow
Tux's lil' helper
Joined: 08 Sep 2019
Posts: 116
|
| Posted: Mon Apr 21, 2025 8:18 pm Post subject: |
|
|
| grknight wrote: | | Code: | (dev-python/setuptools-78.1.0:0/0::gentoo, ebuild scheduled for merge) USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_11 python3_13 (-pypy3) (-pypy3_11) -python3_10 -python3_12 (-python3_13t)" conflicts with
>=dev-python/setuptools-78.1.0[python_targets_python3_11(-),python_targets_python3_12(-)] required by (dev-python/i3ipc-2.2.1-r1:0/0::guru, installed) USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_11 python3_12" |
This is your problem: dev-python:i3ipc::guru is not python 3.13 ready (at least as the ebuild is written)
Either i3ipc needs to be updated or else setuptools and other dependencies need to have both 3.12 and 3.13 enabled at the same time until it is. |
OK....I went to each listed dependency conflict and went to /etc/portage/package.use for each one and listed python3_12 python3_13
I then reran the update command and I still have the dependency conflicts. What am I doing wrong?
for python in package.use I have the following as per the "safer" update protocol:
*/* PYTHON_TARGETS: -* python3_13
*/* PYTHON_SINGLE_TARGET: -* python3_13
Is this correct?
here is the update command:
https://bpa.st/OFRQ |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 2118
|
| Posted: Mon Apr 21, 2025 8:29 pm Post subject: |
|
|
Oh, I missed | Code: | | >=dev-python/gpep517-13[python_targets_python3_11(-)] required by (x11-misc/autotiling-1.8:0/0::guru, installed) USE="" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_11 -python3_10" |
This needs python 3.11 only and all dependencies with 3.11, 3.12 and 3.13 (or just drop it if possible since it seems very neglected)
| eklebanow wrote: | | I then reran the update command and I still have the dependency conflicts. What am I doing wrong? |
Nothing is wrong except for packages that are not very well maintained in an overlay. |
|
| Back to top |
|
|
eklebanow
Tux's lil' helper
Joined: 08 Sep 2019
Posts: 116
|
| Posted: Mon Apr 21, 2025 8:36 pm Post subject: |
|
|
| grknight wrote: | Oh, I missed | Code: | | >=dev-python/gpep517-13[python_targets_python3_11(-)] required by (x11-misc/autotiling-1.8:0/0::guru, installed) USE="" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_11 -python3_10" |
This needs python 3.11 only and all dependencies with 3.11, 3.12 and 3.13 (or just drop it if possible since it seems very neglected)
| eklebanow wrote: | | I then reran the update command and I still have the dependency conflicts. What am I doing wrong? |
Nothing is wrong except for packages that are not very well maintained in an overlay. |
So...are you saying everything is OK.....I should just ignore the dependency conflicts?
How do I drop "autotiling"? something like emerge --deselelect OR emerge --unmerge?? |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23356
|
| Posted: Mon Apr 21, 2025 9:14 pm Post subject: |
|
|
The dependency conflict means what the warning says: there are updates available, which you cannot install because they would violate the dependency constraints. If you want those updates, solve the dependency constraint. If you don't want the updates, ignore it.
You should only use emerge --unmerge if you can explain why that is the right choice. If you need to ask, stick to emerge --ask --verbose --depclean, which will only let you remove things that can be removed without causing dependency problems. |
|
| Back to top |
|
|
|
Portage & Programming
