Am 15.06.2017 um 03:53 schrieb Neil Rickert:
On 06/14/2017 03:19 PM, Frank Krüger wrote:
Rebooting and applying the purge-kernels service removes the standard kernel-default-4.4.69-2.3 as expected. However, using "zypper dup" tries to install the standard kernel again.
That's not quite right.
The previous kernel was actually "kernel-default-4.4.69-2.2". That was replaced by "kernel-default-4.4.69-2.3" I did not have kernel-default-4.4.69-2.2 installed before (see below)
The new kernel is a recompile of the same kernel as before. The two cannot co-exist. Both of them will have the kernel stored as "/boot/kernel-default-4.4.69-2", and that would give a conflict. So the older kernel was actually removed by "zypper" during your update. The "purge-kernels" service did not have anything to do.
You are probably right, that you have not seen this happen with 42.2. But we do often see it happen with Tumbleweed. Once the final release of 42.3 is out, you probably won't see this happen. But the development is being handled similarly to Tumbleweed, so these recompiles may occur again during the development phase.
I hope that helps explain what you are seeing, and why it isn't a problem.
Thank you for your explanation. The issue I experience, however, is the following (using kernel stable repo): rpm -q kernel-default: kernel-default-4.11.4-1.1.gcba98ee.x86_64 kernel-default-4.11.5-1.1.g8ffa6bb.x86_64 as expected, since I have multiversion.kernels = latest,latest-1,running. Applying "zypper dup" pulls in kernel-default-4.4.69-2.3, which will be removed after a reboot with purge-kernels.service. This does not make sense at all in my opinion. Any idea? Regards, Frank -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org