Made a couple of very basic changes as discussed in the morning. Getting familiar with the workflow as well. PR: https://pagure.io/pungi-fedora/pull-request/380

https://pagure.io/pungi-fedora/pull-request/387 Moving the same changes to f 27 branch.

https://pagure.io/pungi-fedora/pull-request/391#
configure 32 bit arm images using apliance-creator

Do we have an ETA for all these changes? Can we help somehow, perhaps?

Added new kickstart file, PR: https://pagure.io/fedora-kickstarts/pull-request/295#
Updated conf file to use new kickstart file, PR: https://pagure.io/pungi-fedora/pull-request/393

Rawhide - > Bikeshed rename RPs:
https://pagure.io/pungi-fedora/pull-request/392
https://pagure.io/pungi-fedora/pull-request/394

Bikeshed rsyncing PR:
https://pagure.io/pungi-fedora/pull-request/395

32bit arm image PRs:
https://pagure.io/pungi-fedora/pull-request/391
https://pagure.io/pungi-fedora/pull-request/393

Getting rid of live_target and use global setting. PR : https://pagure.io/pungi-fedora/pull-request/396

I see that /usr/share/mash/spam-o-matic reports are generated successfully, for example:

/mnt/koji/compose/Fedora-Modular-Bikeshed-20171009.n.0/logs/depcheck

and changelogs as well:

/mnt/koji/compose/Fedora-Modular-Bikeshed-20171009.n.0/logs/changelog-Fedora-Modular-Bikeshed-20171009.n.0.brief

@ausil, should I proceed and migrate over the # Tell everyone by email about the compose part from nightly.sh too?

@tmlcoch we should proceed to that. I am not sure we should add the depcheck for now as the deps are really badly broken.

@ausil, About the "setup empty repos for updates and updates-testing for fedora 27".

My understanding of this issue is:

• Create two new pungi config files, one for update other for updates-testing.
• Create a shell script for each of them, analogue of nightly-modular.sh, that will syncs these two new composes to /pub/fedora/linux/modular/updates/27/ and /pub/fedora/linux/updates/testing/27/

Is my understanding correct? Did I miss anything?

@tmlcoch we need to work with @bowlofeggs to make what we setup mesh with what bodhi will be doing, we will need to extend https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/bodhi2/backend/files/fedora-updates-push or add a new fedora-modular-updates-push script to do the syncing. we will manually run it once, to setup and sync the empty compose in place

PR for the email reports:
https://pagure.io/pungi-fedora/pull-request/400

IRC chat with ausil, follow up to do -
Backport all the above changes to F27 branch.

@rashmin, ack, I will backport all changes that have been done for nightly-modular.sh and fedora-modular.conf in pungi-fedora repo when the https://pagure.io/pungi-fedora/pull-request/400 is merged.

Have you already backported anything? If not, could you please changes you have done on fedora-kickstarts repo (fedora-modular-arm-server.ks).

I have created a PR with all the necessary kickstarts including the one for arm:

https://pagure.io/fedora-kickstarts/pull-request/301

PR with master -> f27 backport in pungi-fedora repo opened:
https://pagure.io/pungi-fedora/pull-request/403
Modular compose config and sh scripts are updated to match master.

@tmlcoch @rashmin The F27 Beta config will be the same as fedora-modular.conf with deltarpms turned off

PR for the F27 beta config:
https://pagure.io/pungi-fedora/pull-request/405

PR for release-candidate-modular.sh for f27 branch:
https://pagure.io/pungi-fedora/pull-request/408

@tmlcoch @rashmin
Based on this ticket and conversations I've had with @mohanboddu/@rashmin, it appears the work the F27 beta compose configs is complete, and we are waiting and prepping for the F27 RC request which will come from QA or the modularity team at some point.

@mohanboddu reports that this ticket can be closed because we are not doing these composes anymore.