> > To deal with the cloud image issue I was originally going to resolve > > it slightly differently, I've not dealt with it in oz. the current > > "Fedora version" that pungi specifies (F-22) now retains BIOS by > > default, to use UEFI you can specify F-30 and if edk2 is available it > > will use that by default. > > > > So I'd like to upgrade the builders to oz-0.17.0-0.2.fc29 > > +1. I assume there will be a pungi-fedora PR to switch from Fedora-22 to > Fedora-30 for those things that want to use this? :) Eventually yes, as it only affects x86 ATM it doesn't affect any of the standard Fedora deliverables so no actual need of change and we want it left as F-22. The IoT pungi config is currently elsewhere. In the case of ARMv7/aarch64 it works as for both those arches UEFI is the only way they've ever worked so they don't need change either. Eventually I might get the enthusiasm and come cycles to make the cloud images more generic and able to run on UEFI platforms but ATM I don't have the cycles to begin to care about that so I'll leave that, at least for the time being, to those that might. P _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
