You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Secure Boot packages (fwupd, fwupd-efi, grub2, pesign) can only be correctly built by being assigned to the secure-boot channel, which requires special privileges which very few have. They are supposed to use package.cfg files so that the rawhide build also kicks off a simultaneous eln build, as EBS cannot do so.
However, this does not seem to be running recently, and all these packages have fallen behind rawhide. The cause needs to be determined, and then fixed so that builds continue to be updated. We will need to work with someone who has the necessary privileges to catch them up too.
The text was updated successfully, but these errors were encountered:
I'm not sure why the pesign and grub2 ones didn't build though; they had the correct package.cfg in place. I'm reaching out to nfrayer to build them and hopefully help identify why they didn't get built.
What does the ELN SIG need to do?
The Secure Boot packages (fwupd, fwupd-efi, grub2, pesign) can only be correctly built by being assigned to the
secure-boot
channel, which requires special privileges which very few have. They are supposed to usepackage.cfg
files so that the rawhide build also kicks off a simultaneous eln build, as EBS cannot do so.However, this does not seem to be running recently, and all these packages have fallen behind rawhide. The cause needs to be determined, and then fixed so that builds continue to be updated. We will need to work with someone who has the necessary privileges to catch them up too.
The text was updated successfully, but these errors were encountered: