So I had a look some more and this is still going to fail, it needs changes in fwupd too.
If you want to see this happen, I'll need you to help with a few things: 0) Does riscv64 have the concept of UEFI secure boot? If not, then we need to think about what gets signed lots of various code paths in fwupd and fwupd-efi. My template packaging changes might not even make sense anymore. 1) What is the suffix for EFI binaries on riscv64? I looked and don't see GRUB or SHIM building binaries for it. 2) Please submit a patch to fwupd upstream with the support for this suffix here: https://github.com/fwupd/fwupd/blob/204da7a7750d1fa126f3cb913372446821eb6d0b/plugins/uefi- capsule/fu-uefi-common.c#L18 3) can you please make sure that both fwupd and fwupd-efi source packages can build on riscv64 and don't need other code changes? I'll help land any changes that are needed upstream, but I'll need you to find them first. ** Changed in: fwupd-efi (Ubuntu) Assignee: Mario Limonciello (superm1) => Heinrich Schuchardt (xypron) ** Changed in: fwupd-efi (Ubuntu) Status: Fix Committed => Triaged ** Also affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Changed in: fwupd-signed (Ubuntu) Status: New => Invalid ** Changed in: fwupd (Ubuntu) Status: New => Triaged ** Changed in: fwupd (Ubuntu) Assignee: (unassigned) => Heinrich Schuchardt (xypron) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939138 Title: Fwupd missing uefi plugin for riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1939138/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
