Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57043 - [efivar] Add an upstream patch

Attached to Project: Arch Linux
Opened by Bruno Pagani (ArchangeGabriel) - Wednesday, 10 January 2018, 22:58 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 27 February 2018, 17:52 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

https://github.com/rhboot/efivar/commit/cd732494ba7685feaf71b9ee58619ca6aef39fc9 is required for fwupdate 10 to compile.

This fwupdate release fixes an important issue for Arch users, namely the possibility to use a different path than /boot/efi/ for the ESP, such as /boot directly which is very common on Arch. So I’d like to get it out as soon as possible, hence my request to add this upstream patch without waiting for a new upstream release.
This task depends upon

This task blocks these from closing
 FS#55815 - [fwupdate] Uses wrong efi path during installation 
Closed by  Tobias Powalowski (tpowa)
Tuesday, 27 February 2018, 17:52 GMT
Reason for closing:  Fixed
Comment by Mario (superm1) - Monday, 05 February 2018, 20:05 GMT
I'd like to echo the importance of this. I'm coming from upstream and we're analyzing firmware failure reports.
This bug is blocking  FS#55815  which is directly leading to install failures that we're seeing reported upstream (see duplicate  FS#57382 )
Comment by Daenney (daenney) - Saturday, 10 February 2018, 15:45 GMT
There's a pending request for upstream to properly tag an efivars 33 release: https://github.com/rhboot/efivar/issues/96. That would obviate the need to pull this patch in. We could get a newer efivars instead and unblock the fwupdate 10 update. I'd love to flag efivar out of date but without a proper release I don't feel I can.
Comment by Mario (superm1) - Tuesday, 13 February 2018, 17:41 GMT
Upstream tagged 34 release, so I'll flag efivar out of date now.
Comment by Mario (superm1) - Tuesday, 27 February 2018, 14:56 GMT
This can be closed since 34 is now in testing.

Loading...