@ malcolmlewis I do use the ZFS packages from the filesystem repo, and it’s awesome that they get built. The problem with those is that they always get built, no matter what the real max supported kernel version is for a particular ZFS release. The current zfs-2.1.9 only officially supports up to kernel 6.1. That will change soon and the next update will support 6.2.x.
Kernel control needn’t be complicated:
/boot # systemctl status purge-kernels
○ purge-kernels.service
Loaded: masked (Reason: Unit purge-kernels.service is masked.)
Active: inactive (dead)
/boot # zypper ll | grep ern
19 | kernel-de* | package | (any) |
/boot # grep CPE /etc/os-release
CPE_NAME="cpe:/o:opensuse:tumbleweed:20230317"
/boot # rpm -q kernel-default
kernel-default-5.4.12-1.1.x86_64
kernel-default-5.5.13-1.2.x86_64
kernel-default-5.6.14-1.6.x86_64
kernel-default-5.7.11-1.2.x86_64
kernel-default-5.8.15-1.2.x86_64
kernel-default-5.9.14-1.2.x86_64
kernel-default-5.10.16-1.3.x86_64
kernel-default-5.11.16-1.1.x86_64
kernel-default-5.12.13-1.1.x86_64
kernel-default-5.13.12-1.2.x86_64
kernel-default-5.14.14-3.3.x86_64
kernel-default-5.15.12-1.3.x86_64
kernel-default-5.16.15-1.1.x86_64
kernel-default-5.17.9-1.1.x86_64
kernel-default-5.18.15-1.1.x86_64
kernel-default-5.19.13-1.1.x86_64
kernel-default-6.0.12-1.1.x86_64
kernel-default-6.1.12-1.1.x86_64
kernel-default-6.2.1-1.1.x86_64
/boot # zypper rm kernel-default-5.4.12
...
Problem: conflicting requests
Solution 1: do not ask to delete all solvables providing kernel-default.x86_64 = 5.4.12-1.1
Solution 2: remove lock to allow removal of kernel-default-5.4.12-1.1.x86_64
Choose from above solutions by number or cancel [1/2/c/d/?] (c):
Answering 2 will remove kernel-5.4.12, but the kernel-de* lock will remain in place.
/boot # zypper in kernel-default-6.2.6
...
Problem: conflicting requests
Solution 1: do not ask to install a solvable providing kernel-default.x86_64 = 6.2.6-1.1
Solution 2: remove lock to allow installation of kernel-default-6.2.6-1.1.x86_64[OSS]
Choose from above solutions by number or cancel [1/2/c/d/?] (c): c
Answering 2 will result in kernel-default-6.2.6 being installed, but the kernel-de* lock will remain.
Thus on this TW installation, there is no risk of installation or removal of any kernel-default except at the direction of the admin.
Of course they do - they prevent removal of these packages matching locks.
That is not how locks work. Locking package “foo” at version “N” does not prevent installing package “foo” version “N+1”, as long as it does not require removal of version “N”.
There is nothing about “keeping exact version” in zypper manual either.