On Mon, Oct 21, 2019 at 11:45:18AM -0400, Owen Taylor wrote: > One of the main goals for Fedora 31 Silverblue was to have core > applications that were removed a few releases ao from the Silverblue > fixed image because they could be installed as Flatpaks actually > pre-installed when you install Silverblue. The anaconda feature landed > this cycle, and we have all the applications available as > Fedora-infrastructure built Flatpaks, so the last missing piece was > getting the ostree-installer config updated appropriately > > We tried to squeeze this in before the final freeze, but there were > some bugs in the configuration and templates that didn't quite work - > those are all fixed and tested in rawhide, and we'd like to backport > to F31. > > There are three things that we need: > * Backport fixes to the lorax template: > https://pagure.io/fedora-lorax-templates/pull-request/44 > * Backport fixes to the Pungi config: > https://pagure.io/pungi-fedora/pull-request/783 > * Update Pungi on the F31 compose VM to a version that includes the > patch from https://pagure.io/pungi/pull-request/1278 - this was > already done on the VM that runs rawhide composes. > > Note that Silverblue is *not* a release-blocking deliverable for > Fedora 31. I think the risk to the overall compose is pretty small, > given that everything here is a direct backport from Rawhide, and > caused no problems there. Given that this should only affect silverblue, I am +1. Note tho: If you also want this in GA f31, we would need to modify the pungi config for that too right? (fedora-final.conf) kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
