Some packages that have kernel.d hooks are always trying to modify vmlinuz-${version} even if dracut-uefi is used.

Is this a new report?

Yes

System Info

Void 6.6.63_1 x86_64 AuthenticAMD uptodate rFF

Package(s) Affected

efibootmgr-18_1, sbsigntool-0.9.4_6

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No response

Expected behaviour

The packages should include a configurable hook in /etc/default, that allows a user to set the file path of the /etc/kernel.d script, so that UKIs or non standard vmlinuz paths can be affected by these hooks. The file /efi/EFI/BOOT/void/Linux-${VERSION} should be just as affected as the default /boot/vmlinuz-${VERSION}

Actual behaviour

Due to the hardcoded nature of the file paths, only /vmlinuz-${VERSION} is affected by these scripts.

Steps to reproduce

1. Install dracut-uefi and the affected packages (efibootmgr-18_1, sbsigntool-0.9.4_6)
2. configure the packages using /etc/default to your liking
3. run xbps-reconfigure -fa
4. Notice that the UKI neither gets registered by efibootmgr, nor gets signed by sbsigntool

Start by inspecting the efibootmgr-18_1 and sbsigntool-0.9.4_6 package hooks, their /etc/default configuration, and the /etc/kernel.d scripts used during xbps-reconfigure -fa. Verify how dracut-uefi names the UKI at /efi/EFI/BOOT/void/Linux-${VERSION}; done means the configured hook path handles that file as well as the default /boot/vmlinuz-${VERSION}.