On 2023-01-09 16:38:34 Glen Barney wrote:
|I have a number of 15.4 servers, which have been upgraded from previous | recent Leap versions. These servers have the legacy Python 2.7, the | current Python 3.6, and the newer Python 3.9 package groups all | installed, side by side, and all working properly. | |However.... attempts to install Python 3.10 fail, with what appear to be | dependency conflicts against Python 3.9, as shown: | |# zypper install python310 |Loading repository data... |Reading installed packages... |Resolving package dependencies... |Problem: the installed python39-setuptools-44.1.1-7.3.1.noarch requires | 'python39', but this requirement cannot be provided not installable | providers: python39-3.9.10-150300.4.8.2.x86_64[repo-oss] | python39-3.9.10-150300.4.8.2.x86_64[repo-sle-update] | python39-3.9.13-150300.4.13.1.x86_64[repo-sle-update] | python39-3.9.14-150300.4.16.1.x86_64[repo-sle-update] Solution 1: | Following actions will be done: | deinstallation of python39-setuptools-44.1.1-7.3.1.noarch | deinstallation of python39-pip-20.2.4-7.8.1.noarch | deinstallation of libpython3_9-1_0-3.9.15-150300.4.21.1.x86_64 | Solution 2: do not install python310-3.10.8-150400.4.15.1.x86_64 | Solution 3: break python39-setuptools-44.1.1-7.3.1.noarch by ignoring | some of its dependencies | |I have even tried downloading the 8 "main" Python310 packages and | installing via rpm... | |libpython3_10-1_0-3.10.8-150400.4.15.1.x86_64.rpm |python310-3.10.8-150400.4.15.1.x86_64.rpm |python310-base-3.10.8-150400.4.15.1.x86_64.rpm |python310-curses-3.10.8-150400.4.15.1.x86_64.rpm |python310-dbm-3.10.8-150400.4.15.1.x86_64.rpm |python310-devel-3.10.8-150400.4.15.1.x86_64.rpm |python310-pip-22.0.4-150400.3.3.1.noarch.rpm |python310-setuptools-57.4.0-150400.2.14.noarch.rpm | |# rpm -Uvh [lp]* |error: Failed dependencies: | python39 is needed by (installed) | python39-setuptools-44.1.1-7.3.1.noarch python39 = 3.9.15 is needed by | (installed) python39-tk-3.9.15-150300.4.21.1.x86_64 python39 = 3.9.15 is | needed by (installed) python39-testsuite-3.9.15-150300.4.21.1.x86_64 | python(abi) = 3.9 is needed by (installed) | python39-setuptools-44.1.1-7.3.1.noarch python(abi) = 3.9 is needed by | (installed) python39-pip-20.2.4-7.8.1.noarch python(abi) = 3.9 is needed | by (installed) python39-tools-3.9.15-150300.4.21.1.x86_64 python(abi) = | 3.9 is needed by (installed) python39-tk-3.9.15-150300.4.21.1.x86_64 | python(abi) = 3.9 is needed by (installed) | python39-testsuite-3.9.15-150300.4.21.1.x86_64 python39-base >= 3.9.15 is | needed by (installed) libpython3_9-1_0-3.9.15-150300.4.21.1.x86_64 | python39-base = 3.9.15 is needed by (installed) | python39-tools-3.9.15-150300.4.21.1.x86_64 /usr/bin/python3.9 is needed | by (installed) python39-setuptools-44.1.1-7.3.1.noarch /usr/bin/python3.9 | is needed by (installed) python39-pip-20.2.4-7.8.1.noarch | /usr/bin/python3.9 is needed by (installed) | python39-tools-3.9.15-150300.4.21.1.x86_64 | |I've listed out the contents of the existing Python3.9 packages, as well | as the manually-downloaded Python3.10 packages. All seem to be properly | structured, in that they all install with separate names and/or in | separate directories, just as expected. Nevertheless it appears that | any attempts to install Python3.10 make the servers try to uninstall | Python3.9, which implies that, despite the separate layouts and | structures, the two versions cannot be installed side-by-side. | |I'm sure I am missing something obvious. Can anyone please help me get | Python 3.10 deployed alongside Python 3.9 (and the other versions) on | Leap 15.4? | |Thank you! |Glen
If, as you say, there are no collisions between the 3.9 and 3.10 packages, perhaps | # zypper --force install ... might do the trick? Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 x86_64