> 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'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

Leslie -

Thank you so much for your reply.  Alas, the force flag did not help:

# zypper install --force python310

Retrieving repository 'Update repository with updates from SUSE Linux Enterprise 15'[done]

Building repository 'Update repository with updates from SUSE Linux Enterprise 15' c[done]

Loading repository data...

Reading installed packages...

Forcing installation of 'python310-3.10.8-150400.4.15.1.x86_64' from repository 'Update repository with updates from SUSE Linux Enterprise 15'.

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

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):

I think the problem is not so much with installing 310 as it is with the

apparently-required removal of 39, and the breakages that such removals

would entail.

Ideally I'd like to install 310 without removing 39 (and without breaking

the 39 deployment in the process.)  I'm confused as to why there is so much

insistence in these packages that 39 must be removed before 310 can be

Any ideas from you and/or anyone on this list would be most appreciated!

Thanks,

Glen