Timothée Ravier

We reverted the change in Ignition in https://github.com/coreos/ignition/pull/2163. The plan is likely to: - Add support for a `file://` scheme in Ignition to tell it to read files from what...

From a side discussion, it's not great that are hardcoding in the code what components should be in the image as this will likely vary in the future and does...

OK let's revert that change and add the checks per-architecture in https://gitlab.com/fedora/bootc/base-images/-/blob/main/minimal/bootupd.yaml?ref_type=heads#L36 instead

Moving the check on the image building side would look like: https://pagure.io/workstation-ostree-config/pull-request/718. Maybe we should add command line arguments to `generate-metadata` to tell bootupd to fail if something is missing:...

https://github.com/coreos/bootupd/pull/1021#issuecomment-3550193095: > @travier the command that we want to use is for package mode, also for image mode, is this right? This command will be used exclusively on package mode.

I have not reviewed the code yet, but in the meantime, can you test that this change works when you run it as part of a GRUB update? See `%posttrans`...

From a discussion with Huijing, it would be good to test this end to end on a Fedora package mode VM with a GRUB update with the change in the...

> Just one small question about this, after install the new bootupctl, `/boot/efi` is unmounted, maybe we should not unmount (the same as before installation)? WDYT? @travier Ah yes, when...

You also have an override file that you probably don't want there: overrides/rootfs/usr/libexec/ignition-apply

We would probably need to extend to the current JSON status format to include a board/firmware ID that would then be resolved to a list of firmwares in the image...