https://bugzilla.redhat.com/show_bug.cgi?id=2134972 --- Comment #14 from Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> --- > It should be possible to rpm -qf, and more importantly, rpm -Vf absolutely everything in the boot path. This does not work currently and is not intended to work. It currently does not work because the initrds are generated locally, so 'rpm -Vf' cannot check their contents. More broadly, the ESP (or XBOOTLDR) are intended to be shared between installations in dual boot scenarios, and one of those installations should just ignore the other ones. If boot counting [1] is implemented (and there are good reasons to do that), the boot count is part of the file name, and this just can't be handled by 'rpm -Vf'. [1] https://github.com/uapi-group/specifications/blob/main/specs/boot_loader_specification.md#boot-counting Hardcoding of /boot and /boot/efi is problematic because there are good reasons to swith a different path in the future. If we do that, effectively we'll have to support multiple layouts — both the new one, but also the old one for compatibility. Locking ourselves into a specific layout via packaging now is borrowing trouble. > including the creation of that simlink required to assure that kernel upgrades work That symlink is NOT required for kernel upgrades to work. It is used by 'make install' in local kernel builds. Kernel package scripts use kernel-install. > Are you signing up to add this functionality to systemd-boot, or merge this stuff there? I cannot give a blanket promise to merge things. I can promise to review pull requests and maybe work on some feature requests. At this point, I don't quite understand what is missing from sd-boot. If there's some general bug or missing feature, we'll do our best to solve it like any other issue. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2134972 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue