Comments

23 Comments

systemd (sd-boot) cannot built with this.

This should work with gnu-efi-3.0.11-2.fc31, except that due to a bugfix in one of the type definitions (to match what edk2 does), I needed to apply the following patch:

diff --git src/boot/efi/util.c src/boot/efi/util.c
index da743dcb9f2..f91462ae636 100644
--- src/boot/efi/util.c
+++ src/boot/efi/util.c
@@ -184,7 +184,7 @@ VOID efivar_set_time_usec(CHAR16 *name, UINT64 usec) {
         efivar_set(name, str, FALSE);
 }

-static INTN utf8_to_16(CHAR8 *stra, CHAR16 *c) {
+static INTN utf8_to_16(UINT8 *stra, CHAR16 *c) {
         CHAR16 unichar;
         UINTN len;
         UINTN i;

All of the "E:" error cases in the rpmlint failure are, in fact, completely wrong. The warnings about the non-devel-package bits are true, in that we should merge them at some point, but ultimately meaningless as it's not a change between this build and older ones. The "patch not applied" warnings are because rpmlint in f30 doesn't understand "%autosetup -S git_am".

All of the "E:" error cases in the rpmlint failure are, in fact, completely wrong. The warnings about the non-devel-package bits are true, in that we should merge them at some point, but ultimately meaningless as it's not a change between this build and older ones.

Note that the pesign-test-app build was built with this pesign version, so it must have worked.

Can anyone experiencing a problem here answer https://bugzilla.redhat.com/show_bug.cgi?id=1773175#c1 ?

karma

Works for me, and fixes the signing issue.

The build at https://koji.fedoraproject.org/koji/taskinfo?taskID=24121627 should fix the gnome-software issue; you'll need to restart fwupd.service and gnome-software. I think @rhughes should have an update filed soon.

"i have a dell XPS 13 9360. It works for me, it has successfully updated the bios by running fwupdmgr. However, as a side point, updates via Gnome Software do not work, it doesn't seem to notice there are updates at all. I've reported this separately."

I'm seeing the same thing, and @rhughes is investigating that now, though so far it appears unrelated to this update.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.