@njmike73 Just wanted to chip in here re:
That is the linux kernel version (package version actually) that you are running. As a result of:
Which likely comes from the following howto:
Installing the Stable Kernel Backport: Installing the Stable Kernel Backport — Rockstor documentation
and you have the associated newer filesystems repository also to match the newer version of the kernel than is found in standard Leap:
And regarding:
Could you tell us the history of this install, i.e. was it once a 15.3, and if so did you update it according to the following howto:
Distribution update from 15.3 to 15.4: Distribution update from 15.3 to 15.4 — Rockstor documentation
Don’t do anything just yet, but it may help for context. Some of the packages involved in this criss-cross of dependencies look like they come from a 15.3, just exploring what may have happened here to help explain what has gone strange.
Incidentally we shall soon be updating our python dependency so this may just go away. But still good to know how it came-to-be. Plus openSUSE Leap are in the throws of introducing a Python 3.11 package set, so we hope to be moving to that.
From a quick look here, it looks like the python3.10 they have introduced along the way, native to 15.4 (python310-base-3.10.13-150400.4.36.1.x86_64) is seen as conflicting with the 3.9 that we depend upon in our testing rpm.
Also note that sometimes a:
zypper refresh
can help, as it refreshes the local database on what is available and what depends on what. This changes all the time. Rockstor will have done that already however, but it may help to try it at the terminal to see if some repository has changed its signing key or the like.
On a Leap 15.4 system I have here I get the following for the Py3.9 dev package:
rleap15-4:~ # zypper se -s python39-devel
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+----------------+---------+----------------------+--------+-------------------------------------------------------------
i+ | python39-devel | package | 3.9.18-150300.4.33.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.17-150300.4.30.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.16-150300.4.27.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.16-150300.4.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.15-150300.4.21.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.14-150300.4.16.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.13-150300.4.13.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.10-150300.4.8.1 | x86_64 | Main Repository
v | python39-devel | package | 3.9.10-150300.4.8.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
And actaully they look to have a 150300 ending like yours so that may be a read herring.
Hand in there, you are still likely able to put in all other updates and we are on the move re dependencies currently. Plus soon you will be looking at a distribution update to 15.5 anyway given the near end of life (EOL) for Leap 15.4. I’ve not yet written the howto for that one however.
Incidentally the above Leap 15.4 example does allow for a 5.0.5 to be installed as we have the following:
rleap15-4:~ # zypper info rockstor
Loading repository data...
Reading installed packages...
Information for package rockstor:
---------------------------------
Repository : Local-Repository
Name : rockstor
Version : 5.0.5-2727
Arch : x86_64
Vendor : YewTreeApps
Installed Size : 7.7 MiB
Installed : Yes
Status : up-to-date
Source package : rockstor-5.0.5-2727.src
Upstream URL : https://rockstor.com/
Summary : Btrfs Network Attached Storage (NAS) Appliance.
Description :
Software raid, snapshot capable NAS solution with built-in file integrity protection.
Allows for file sharing between network attached devices.
Which is a development RPM build to ensure installability etc for the now merged 2727 pull request.
Sorry no answers, but we are moving on these things and this may just go away with our next Python dependency update, or a plain old zypper refresh, try that at the command line and let us know here what it states. If it asks to update signing keys they you can agree given the list of repositories you have (they are all official ones).
It may do, not sure in this case as this is part of Leaps ongoing Python update, however Py3.9 and Py3.10 should be able to co-exist. But they are moving to providing Py3.11 which we hope to jump on with our current efforts, but many moving parts currently as we are still mid testing phase so this sort of thing can crop up and then just go away.
Hope that helps, at least for some context.
