Hi All,
Fedora 35 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f36 has been completely isolated from previous releases, so this means that anything you do for f35 you also have to do in the rawhide branch and do a build there. There will be a Fedora 35 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/35/ once complete. Please be sure to check it out. Bodhi is currently not active for Fedora 35, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 35 schedule[1].
Two things to remember:
1. The modules will be built for a new platform:f36 2. The signing of rpms is not done yet with the new f36 key. 3. F35/branched release is frozen right now until we get a successful compose, expect that your f35 builds won't be available immediately.
Thanks for understanding.
[1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
V Tue, Aug 10, 2021 at 04:33:03PM -0400, Mohan Boddu napsal(a):
- The modules will be built for a new platform:f36
The empty commits into the modules I observe are pointless:
Either a module uses a stream expansion (platform:[]) and then just resubmitting the last build is enough for MBS to discover f36 platform and build the module from exactly the same RPM sources which were used for the last module build. In other words, MBS is smart enough and will build a context for platform:f36.
Or the module lists platforms explicitly (platform:[f34, f35]) and then no empty commit will help you in building the module for f36 platform. You would have to add "f36" to all the platform lists found in the modulemd file (all cases of build- and requires).
By the way, many Perl modules will fail to build now because I migrated them to a new modulemd-packager-v3 format and it turned out that MBS does not support it well https://pagure.io/fm-orchestrator/issue/1714. I will rever the changes and rebuild them for f36 when I return from my vacation.
-- Petr