On Mon 2022-07-18 02:28:31, Felix Miata wrote:
Manfred Hollstein composed on 2022-07-18 01:56 (UTC-0400):
Felix Miata wrote:
Felix Miata composed on 2022-07-15 19:20 (UTC-0400):
Is $SUBJECT what was supposed to happen?
Prior TW version was 20220630. Newest kernel installed prior to 5.18.9-2 was 5.17.9-1.
June/July portion of /var/log/zypp/history: https://paste.opensuse.org/74203728
Just happened again on dup from 20220613 to 20220714. Latest previous kernel was 5.18.2. :(
Do you know whether the older kernels were removed after "zypper dup" or after "rpm -i kernel-default-5.18.9-2 x86_64"? rpm -i should not remove any package. I guess that it was "zypper dup".
no problems here, all latest dups left all kernels installed. What does /etc/zypp/zypp.conf contain for multiversion.kernels? This is what I have here:
# grep multi /etc/zypp/zypp.conf | egrep -v '^#' multiversion = provides:multiversion(kernel) multiversion.kernels = latest,latest-1,running,oldest
Same here.
I forgot to mention, because I keep kernels locked, none added, none removed, unless and until I choose, this is/was a particularly huge surprise: # grep -B3 kernel /etc/zypp/locks type: package match_type: glob case_sensitive: on solvable_name: kernel-de* -- type: package match_type: glob case_sensitive: on solvable_name: kernel-firmwar?
I wonder if there is a bug in zypper and it ignored these locks. Does "zypper ll" still list the locks?
I know rpm doesn't pay any attention to zypp locks, but I don't recall ever seeing this kind of burn, leaving no kernel to fall back on if the fresh one fails to boot.
I also forgot to mention, I installed 5.18.9-2 using rpm -ivh, which didn't mention anything about any plan to remove anything that caught my attention. :(
Yes, this should not cause the problem. Well, I am not completely sure how zypper handle manually installed packages. I just hope that it does not make any difference. Best Regards, Petr