Hi @jlebon,

Thanks for reporting the above test failure! But I'm not sure how to make sense of the above error! Can you help me understand it?

It means that there is something else in the compose which also installs a file called vmcore-dmesg at the same path (/usr/sbin/vmcore-dmesg), and they are not the same contents. So the two packages conflict.

OK, I think I see what's going on. We're composing with kdump-utils-1.0.42-9.fc41, which is from before the split out into a separate package, and has an older version of that file.

The fix for this is on our side; we really need to get a new rawhide build of FCOS out. But possibly it might also be appropriate for new kexec-tools to be marked as Conflicts: kdump-utils < 1.0.42?

E.g. if a rawhide system has the packages from before the split and the sysadmin did a dnf update kexec-tools, I think they might hit this same issue because nothing forces kdump-utils from also being updated.

As you see from the file list kdump-utils doesn't have /usr/sbin/vmcore-dmesg. This file is always provided by kexec-tools. I imagine when kexec-tools gets updated, the old /usr/sbin/vmcore-dmesg should be replaced by the new version. So think the real problem should lie somewhere else.

As you see from the file list kdump-utils doesn't have /usr/sbin/vmcore-dmesg. This file is always provided by kexec-tools. I imagine when kexec-tools gets updated, the old /usr/sbin/vmcore-dmesg should be replaced by the new version. So think the real problem should lie somewhere else.

It was provided by the kdump-utils subpackage before: https://koji.fedoraproject.org/koji/rpminfo?rpmID=38435162

Thanks for correcting me!

Oh, this is a regression caused by the following commit. Sorry I didn't catch this issue when merging it.

commit e3a1eb06ac40d0d3c83ac15bb78c0094f8dc2b1a (kexec_sbin/bin-sbin-merge)
Author: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date:   Sun Apr 14 19:06:17 2024 +0200

    Fix build when %_bindir==%_sbindir

    Preparation for https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin.
 # makedumpfile

@@ -249,8 +251,9 @@ fi
 %{_sbindir}/mkfadumprd
 %{_prefix}/lib/kernel/install.d/60-fadump.install
 %endif
+%{_bindir}/kdumpctl
 %{_sbindir}/mkdumprd
-%{_bindir}/*
+%{_sbindir}/vmcore-dmesg

The latest kdump-utils has already fixed this issue unintentionally. Since 1) this issue can be bypassed by updating kdump-utils to latest version 2) and only happens to rawhide 3) and you plan to fix it on your side, do you think "Conflicts: kdump-utils < 1.0.42" is still needed? Or what else can I do for you?

Indeed, I think given that this is rawhide it's not worth adding a Conflicts. Thanks!

Thanks for confirming it!

I've released kexec-tools-2.0.28-12.fc41. kexec-tools-2.0.28-10.fc41 should be used because it has the same problem as 2.0.28-10.fc40.