http://bugzilla.opensuse.org/show_bug.cgi?id=1173106 http://bugzilla.opensuse.org/show_bug.cgi?id=1173106#c1 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |nwr10cst-oslnx@yahoo.com --- Comment #1 from Neil Rickert --- I can confirm that. It also happens on Tumbleweed. I previously reported this on bug 1171224 and reopened that bug. The fix for that bug is broken. For now, I have disabled the "purge-kernels" service, and I am manually removing old kernels. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1173106 http://bugzilla.opensuse.org/show_bug.cgi?id=1173106#c3 Manfred Hollstein changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(manfred.h@gmx.net | |) | --- Comment #3 from Manfred Hollstein --- Created attachment 838946 --> http://bugzilla.opensuse.org/attachment.cgi?id=838946&action=edit /var/log/zypper.log This is my /var/log/zypper.log for the last two days. BUT, I never ran purge-kernels explicitly, but just used "zypper dup" for upgrading from one snapshot to the next one, or "zypper up" to install local updates, like the kernels from Kernel:stable (mirrored to my local Kernel:stable.local repo). As Neil suggested, I have disabled "purge-kernels.service" for now, too; will see what'll happen during the next "zypper dup/up" round next time. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1173106 http://bugzilla.opensuse.org/show_bug.cgi?id=1173106#c5 --- Comment #5 from Manfred Hollstein --- The issue is actually triggered by each kernel; their installation script touches /boot/do_purge_kernels: $ rpm -q kernel-default-5.3.18-lp152.19.2.x86_64 --scripts | grep purge # Flag to trigger /etc/init.d/purge-kernels on next reboot (fate#312018) touch /boot/do_purge_kernels rm -f /boot/do_purge_kernels After the next reboot, zypper purge-kernels then gets called and does its job. However, it should *not* remove the devel and source RPMs! Until this is fixed in libzypp/zypper, I'll use this recipe: # systemctl disable purge-kernels.service # zypper dup # rm /boot/do_purge_kernels # reboot -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1173106 http://bugzilla.opensuse.org/show_bug.cgi?id=1173106#c7 Benjamin Zeller changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #7 from Benjamin Zeller --- So it seems that the kernel packages do not provide their exact version in the metadata, e.g. I have kernel 4.12.14-lp151.28.44.1 installed, however in the metadata it only provides: kernel = 4.12.14-lp151.28.44 Hence zypper does not realize that its the same package. So it takes down the kernel-devel package, which in turn also removes the kernel-flavour-devel package. Seems I need to find a different way to match those together. -- You are receiving this mail because: You are on the CC list for the bug.